Deploying to gh-pages from @ 7865566338 🚀

_sources/admin/installation.rst.txt

@@ -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
 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
 
    $ cd ~/Downloads
@@ -64,3 +71,11 @@ If all services are running fine, you can add it to your HTTP server:
 - :ref:`installation apache`
 - :ref:`installation nginx`
 
+.. _git stash: https://git-scm.com/docs/git-stash
+
+.. tip::
+
+   About script's installation options have a look at chapter :ref:`toolboxing
+   setup`.  How to brand your instance see chapter :ref:`makefile setup`.  To
+   *stash* your instance's setup, `git stash`_ your clone's :origin:`Makefile`
+   and :origin:`.config.sh` file .

_sources/utils/index.rst.txt

@@ -41,7 +41,7 @@ Scripts to maintain services often dispose of common commands and environments.
   <lxc-searx.env>` use ::
 
     sudo -H ./utils/lxc.sh cmd -- FORCE_TIMEOUT=0 ./utils/filtron.sh apache install
- 
+
 .. _toolboxing setup:
 
 Tooling box setup

admin/installation.html

@@ -75,6 +75,11 @@ box</span></a> as described below.</p>
 <p>The following will install a setup as shown in <a class="reference internal" href="architecture.html#architecture"><span class="std std-ref">Architecture</span></a>.  First you
 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).</p>
+<p>For the installation procedure, use a <em>sudoer</em> login to run the scripts.  If you
+install from <code class="docutils literal notranslate"><span class="pre">root</span></code>, take into account that the scripts are creating a
+<code class="docutils literal notranslate"><span class="pre">searx</span></code>, a <code class="docutils literal notranslate"><span class="pre">filtron</span></code> and a <code class="docutils literal notranslate"><span class="pre">morty</span></code> 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 <code class="docutils literal notranslate"><span class="pre">/root</span></code>.</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$ <span class="nb">cd</span> ~/Downloads
 $ git clone https://github.com/searx/searx searx
 $ <span class="nb">cd</span> searx
@@ -98,6 +103,12 @@ $ <span class="nb">cd</span> searx
 <li><p><a class="reference internal" href="installation-apache.html#installation-apache"><span class="std std-ref">Install with apache</span></a></p></li>
 <li><p><a class="reference internal" href="installation-nginx.html#installation-nginx"><span class="std std-ref">Install with nginx</span></a></p></li>
 </ul>
+<div class="admonition tip">
+<p class="admonition-title">Tip</p>
+<p>About script’s installation options have a look at chapter <a class="reference internal" href="../utils/index.html#toolboxing-setup"><span class="std std-ref">Tooling box setup</span></a>.  How to brand your instance see chapter <a class="reference internal" href="../dev/makefile.html#makefile-setup"><span class="std std-ref">Makefile setup</span></a>.  To
+<em>stash</em> your instance’s setup, <a class="reference external" href="https://git-scm.com/docs/git-stash">git stash</a> your clone’s <a class="reference external" href="https://github.com/searx/searx/blob/master/Makefile">git://Makefile</a>
+and <a class="reference external" href="https://github.com/searx/searx/blob/master/.config.sh">git://.config.sh</a> file .</p>
+</div>
 </div>
 </div>