Changeset - 7e9e1f3d7a93
[Not reviewed]
default
0 1 0
Mads Kiilerich (mads) - 5 years ago 2020-12-12 23:09:44
mads@kiilerich.com
docs: fix broken ref

7982eac0703d removed too much.
1 file changed with 4 insertions and 2 deletions:
0 comments (0 inline, 0 general)
docs/installation.rst
Show inline comments
 
@@ -57,25 +57,25 @@ repository, use the following commands i
 
        . venv/bin/activate
 
        pip install --upgrade pip setuptools
 
        pip install --upgrade -e .
 
        python3 setup.py compile_catalog   # for translation of the UI
 

	
 
.. note::
 
   This will install all Python dependencies into the virtualenv. Kallithea
 
   itself will however only be installed as a pointer to the source location.
 
   The source clone must thus be kept in the same location, and it shouldn't be
 
   updated to other revisions unless you want to upgrade. Edits in the source
 
   tree will have immediate impact (possibly after a restart of the service).
 

	
 
You can now proceed to :ref:`install-front-end`.
 
You can now proceed to :ref:`prepare-front-end-files`.
 

	
 
.. _installation-virtualenv:
 

	
 

	
 
Installing a released version in a virtualenv
 
---------------------------------------------
 

	
 
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.
 
@@ -114,25 +114,27 @@ An additional benefit of virtualenv is t
 

	
 
   This might require installation of development packages using your
 
   distribution's package manager.
 

	
 
   Alternatively, download a .tar.gz from http://pypi.python.org/pypi/Kallithea,
 
   extract it and install from source by running::
 

	
 
     pip install --upgrade .
 

	
 
- This will install Kallithea together with all other required
 
  Python libraries into the activated virtualenv.
 

	
 
You can now proceed to :ref:`install-front-end`.
 
You can now proceed to :ref:`prepare-front-end-files`.
 

	
 
.. _prepare-front-end-files:
 

	
 

	
 
Prepare front-end files
 
-----------------------
 

	
 
Finally, the front-end files with CSS and JavaScript must be prepared. This
 
depends on having some commands available in the shell search path: ``npm``
 
version 6 or later, and ``node.js`` (version 12 or later) available as
 
``node``. The installation method for these dependencies varies between
 
operating systems and distributions.
 

	
 
Prepare the front-end by running::
0 comments (0 inline, 0 general)