on master help sign in
[doc] document why to use sudoer to run intsallation scripts
c8d2b19Markus Heiser
docs/admin/installation.rst+7
@@ -33,6 +33,13 @@ The following will install a setup as shown in :ref:`architecture`. First you
33need to get a clone. The clone is only needed for the installation procedure
33need to get a clone. The clone is only needed for the installation procedure
34and some maintenance tasks (alternatively you can create your own fork).
34and some maintenance tasks (alternatively you can create your own fork).
35
35
36+For the installation procedure, use a *sudoer* login to run the scripts. If you
37+install from ``root``, take into account that the scripts are creating a
38+``searx``, a ``filtron`` and a ``morty`` user. In the installation procedure
39+these new created users do need read access to the clone of searx, which is not
40+the case if you clone into a folder below ``/root``.
41+
42+
36.. code:: bash
43.. code:: bash
37
44
38 $ cd ~/Downloads
45 $ cd ~/Downloads