Changeset - c819a1e9103b
[Not reviewed]
default
0 2 0
Mads Kiilerich (mads) - 6 years ago 2020-08-24 15:02:16
mads@kiilerich.com
Grafted from: 77d70ff0aa37
docs: clarify the idea of best practice of installing in srv

This was introduced in 03bbd33bc084 as it seems like the best location based on
Filesystem Hierarchy Standard.
2 files changed with 9 insertions and 0 deletions:
0 comments (0 inline, 0 general)
docs/installation.rst
Show inline comments
 
@@ -75,24 +75,28 @@ Installing a released version in a virtu
 
---------------------------------------------
 

	
 
It is highly recommended to use a separate virtualenv for installing Kallithea.
 
This way, all libraries required by Kallithea will be installed separately from your
 
main Python installation and other applications and things will be less
 
problematic when upgrading the system or Kallithea.
 
An additional benefit of virtualenv is that it doesn't require root privileges.
 

	
 
- Don't install as root - install as a dedicated user like ``kallithea``.
 
  If necessary, create the top directory for the virtualenv (like
 
  ``/srv/kallithea/venv``) as root and assign ownership to the user.
 

	
 
  Make a parent folder for the virtualenv (and perhaps also Kallithea
 
  configuration and data files) such as ``/srv/kallithea``. Create the
 
  directory as root if necessary and grant ownership to the ``kallithea`` user.
 

	
 
- Create a new virtual environment, for example in ``/srv/kallithea/venv``,
 
  specifying the right Python binary::
 

	
 
    python3 -m venv /srv/kallithea/venv
 

	
 
- Activate the virtualenv in your current shell session and make sure the
 
  basic requirements are up-to-date by running the following commands in your
 
  bash shell::
 

	
 
    . /srv/kallithea/venv/bin/activate
 
    pip install --upgrade pip setuptools
 

	
docs/overview.rst
Show inline comments
 
@@ -65,24 +65,29 @@ Kallithea can be installed in many diffe
 
  is by default in a ``data`` directory next to the ``.ini`` file. This will
 
  have to be writable by the running Kallithea service.
 

	
 
- A database. The ``.ini`` file specifies which database to use. The database
 
  will be a separate service and live elsewhere in the filesystem if using
 
  PostgreSQL or MariaDB/MySQL. If using SQLite, it will by default live next to
 
  the ``.ini`` file, as ``kallithea.db``.
 

	
 
- A location for the repositories that are hosted by this Kallithea instance.
 
  This will have to be writable by the running Kallithea service. The path to
 
  this location will be configured in the database.
 

	
 
For production setups, one recommendation is to use ``/srv/kallithea`` for the
 
``.ini`` and ``data``, place the virtualenv in ``venv``, and use a Kallithea
 
clone in ``kallithea``. Create a ``kallithea`` user, let it own
 
``/srv/kallithea``, and run as that user when installing.
 

	
 
For simple setups, it is fine to just use something like a ``kallithea`` user
 
with home in ``/home/kallithea`` and place everything there.
 

	
 
For experiments, it might be convenient to run everything as yourself and work
 
inside a clone of Kallithea, with the ``.ini`` and SQLite database in the root
 
of the clone, and a virtualenv in ``venv``.
 

	
 

	
 
Python environment
 
------------------
 

	
 
**Kallithea** is written entirely in Python_ and requires Python version
0 comments (0 inline, 0 general)