<p>The <aclass="reference internal"href="installation-searx.html#installation-basic"><spanclass="std std-ref">Step by step installation</span></a> is good enough for intranet usage and it is a
excellent illustration of <em>how a searx instance is build up</em>. If you place your
instance public to the internet you should really consider to install a
<aclass="reference internal"href="../utils/filtron.sh.html#filtron-sh"><spanclass="std std-ref">filtron reverse proxy</span></a> and for privacy a <aclass="reference internal"href="../utils/morty.sh.html#morty-sh"><spanclass="std std-ref">result proxy</span></a> is mandatory.</p>
<p>Therefore, if you do not have any special preferences, its recommend to use the
<aclass="reference internal"href="installation-docker.html#installation-docker"><spanclass="std std-ref">Docker installation</span></a> or the <aclass="reference internal"href="#installation-scripts">Installation scripts</a> from our <aclass="reference internal"href="../utils/index.html#toolboxing"><spanclass="std std-ref">tooling
box</span></a> as described below.</p>
<divclass="section"id="installation-scripts">
<spanid="id2"></span><h2>Installation scripts<aclass="headerlink"href="#installation-scripts"title="Permalink to this headline">¶</a></h2>
<divclass="sidebar">
<pclass="sidebar-title">Update OS first!</p>
<p>To avoid unwanted side effects, update your OS before installing searx.</p>
<p>The following will install a setup as shown in <aclass="reference internal"href="architecture.html#architecture"><spanclass="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 <codeclass="docutils literal notranslate"><spanclass="pre">root</span></code>, take into account that the scripts are creating a
<codeclass="docutils literal notranslate"><spanclass="pre">searx</span></code>, a <codeclass="docutils literal notranslate"><spanclass="pre">filtron</span></code> and a <codeclass="docutils literal notranslate"><spanclass="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 <codeclass="docutils literal notranslate"><spanclass="pre">/root</span></code>.</p>
<p>This installs searx as described in <aclass="reference internal"href="installation-searx.html#installation-basic"><spanclass="std std-ref">Step by step installation</span></a>.</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$ sudo -H ./utils/searx.sh install all
<li><p><aclass="reference internal"href="installation-apache.html#installation-apache"><spanclass="std std-ref">Install with apache</span></a></p></li>
<li><p><aclass="reference internal"href="installation-nginx.html#installation-nginx"><spanclass="std std-ref">Install with nginx</span></a></p></li>
<p>About script’s installation options have a look at chapter <aclass="reference internal"href="../utils/index.html#toolboxing-setup"><spanclass="std std-ref">Tooling box setup</span></a>. How to brand your instance see chapter <aclass="reference internal"href="settings.html#settings-global"><spanclass="std std-ref">Global Settings</span></a>. To