on master help sign in
[doc] document why to use sudoer to run intsallation scripts

related to: - https://gist.github.com/dalf/60450e19b042bd39b9ce470c095d89b3#gistcomment-3263827 - https://github.com/searx/searx/issues/2013#issuecomment-647132313 - https://github.com/searx/searx/issues/2017#issuecomment-647700327 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>

commitc8d2b19c85ab473f67a8450f01eaeab13beaa392 authorMarkus Heiser <markus.heiser@darmarit.de> dateSun 13 Dec 2020, 15:19 (6 years ago) parent3c4a9c1
1 file changed+7
docs/admin/installation.rst+7
docs/admin/installation.rst+7
@@ -33,6 +33,13 @@ The following will install a setup as shown in :ref:`architecture`. First you
3333need to get a clone. The clone is only needed for the installation procedure
3434and some maintenance tasks (alternatively you can create your own fork).
3535
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+
3643.. code:: bash
3744
3845 $ cd ~/Downloads