mir/searx
2
0
Fork 0
mirror of https://github.com/searx/searx synced 2025-09-01 15:06:02 +00:00
Code Issues Releases Wiki Activity

[doc] document why to use sudoer to run intsallation scripts

Browse Source 
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>
This commit is contained in:
Markus Heiser
2020-12-13 15:19:04 +01:00
parent 3c4a9c1188
commit c8d2b19c85
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/admin/installation.rst
View File

@@ -33,6 +33,13 @@ The following will install a setup as shown in :ref:`architecture`. First you
need to get a clone. The clone is only needed for the installation procedure need to get a clone. The clone is only needed for the installation procedure
and some maintenance tasks (alternatively you can create your own fork). and some maintenance tasks (alternatively you can create your own fork).
For the installation procedure, use a *sudoer* login to run the scripts. If you
install from ``root``, take into account that the scripts are creating a
``searx``, a ``filtron`` and a ``morty`` user. In the installation procedure
these new created users do need read access to the clone of searx, which is not
the case if you clone into a folder below ``/root``.
.. code:: bash .. code:: bash
$ cd ~/Downloads $ cd ~/Downloads