This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<li><p><aclass="reference internal"href="#check-after-installation"id="id7">Check after Installation</a></p></li>
</ul>
</li>
</ul>
</nav>
<sectionid="how-to-update">
<spanid="update-searxng"></span><h2><aclass="toc-backref"href="#id3"role="doc-backlink">How to update</a><aclass="headerlink"href="#how-to-update"title="Link to this heading">¶</a></h2>
<p>How to update depends on the <aclass="reference internal"href="installation.html#installation"><spanclass="std std-ref">Installation</span></a> method. If you have used the
<aclass="reference internal"href="installation-scripts.html#installation-scripts"><spanclass="std std-ref">Installation Script</span></a>, use the <codeclass="docutils literal notranslate"><spanclass="pre">update</span></code> command from the <aclass="reference internal"href="../utils/searxng.sh.html#searxng-sh"><spanclass="std std-ref">utils/searxng.sh</span></a>
<spanid="inspect-searxng"></span><h2><aclass="toc-backref"href="#id4"role="doc-backlink">How to inspect & debug</a><aclass="headerlink"href="#how-to-inspect-debug"title="Link to this heading">¶</a></h2>
<p>How to debug depends on the <aclass="reference internal"href="installation.html#installation"><spanclass="std std-ref">Installation</span></a> method. If you have used the
<aclass="reference internal"href="installation-scripts.html#installation-scripts"><spanclass="std std-ref">Installation Script</span></a>, use the <codeclass="docutils literal notranslate"><spanclass="pre">inspect</span></code> command from the <aclass="reference internal"href="../utils/searxng.sh.html#searxng-sh"><spanclass="std std-ref">utils/searxng.sh</span></a>
<spanid="id2"></span><h2><aclass="toc-backref"href="#id5"role="doc-backlink">Migrate and stay tuned!</a><aclass="headerlink"href="#migrate-and-stay-tuned"title="Link to this heading">¶</a></h2>
<li><p><aclass="extlink-pull reference external"href="https://github.com/searxng/searxng/pull/446#issuecomment-954730358">A comment about rolling release</a></p></li>
</ul>
</aside>
<p>SearXNG is a <em>rolling release</em>; each commit to the master branch is a release.
SearXNG is growing rapidly, the services and opportunities are change every now
and then, to name just a few:</p>
<ulclass="simple">
<li><p>Bot protection has been switched from filtron to SearXNG’s <aclass="reference internal"href="searx.limiter.html#limiter"><spanclass="std std-ref">limiter</span></a>, this requires a <aclass="reference internal"href="settings/settings_redis.html#settings-redis"><spanclass="std std-ref">Redis</span></a> database.</p></li>
<li><p>The image proxy morty is no longer needed, it has been replaced by the
<aclass="reference internal"href="settings/settings_server.html#image-proxy"><spanclass="std std-ref">image proxy</span></a> from SearXNG.</p></li>
<li><p>To save bandwidth <aclass="reference internal"href="settings/settings_ui.html#static-use-hash"><spanclass="std std-ref">cache busting</span></a> has been implemented.
To get in use, the <codeclass="docutils literal notranslate"><spanclass="pre">static-expires</span></code> needs to be set in the <aclass="reference internal"href="installation-uwsgi.html#uwsgi-setup"><spanclass="std std-ref">uWSGI setup</span></a>.</p></li>
</ul>
<p>To stay tuned and get in use of the new features, instance maintainers have to
update the SearXNG code regularly (see <aclass="reference internal"href="#update-searxng"><spanclass="std std-ref">How to update</span></a>). As the above
examples show, this is not always enough, sometimes services have to be set up
or reconfigured and sometimes services that are no longer needed should be
uninstalled.</p>
<divclass="admonition hint">
<pclass="admonition-title">Hint</p>
<p>First of all: SearXNG is installed by the script <aclass="reference internal"href="../utils/searxng.sh.html#searxng-sh"><spanclass="std std-ref">utils/searxng.sh</span></a>. If you
have old filtron, morty or searx setup you should consider complete
uninstall/reinstall.</p>
</div>
<p>Here you will find a list of changes that affect the infrastructure. Please
check to what extent it is necessary to update your installations:</p>
<dlclass="simple">
<dt><aclass="extlink-pull reference external"href="https://github.com/searxng/searxng/pull/1595">PR 1595</a>: <codeclass="docutils literal notranslate"><spanclass="pre">[fix]</span><spanclass="pre">uWSGI:</span><spanclass="pre">increase</span><spanclass="pre">buffer-size</span></code></dt><dd><p>Re-install uWSGI (<aclass="reference internal"href="../utils/searxng.sh.html#searxng-sh"><spanclass="std std-ref">utils/searxng.sh</span></a>) or fix your uWSGI <codeclass="docutils literal notranslate"><spanclass="pre">searxng.ini</span></code>
file manually.</p>
</dd>
</dl>
<sectionid="remove-obsolete-services">
<h3><aclass="toc-backref"href="#id6"role="doc-backlink">remove obsolete services</a><aclass="headerlink"href="#remove-obsolete-services"title="Link to this heading">¶</a></h3>
<p>If your searx instance was installed <em>“Step by step”</em> or by the <em>“Installation
scripts”</em>, you need to undo the installation procedure completely. If you have
morty & filtron installed, it is recommended to uninstall these services also.
In case of scripts, to uninstall use the scripts from the origin you installed
searx from or try:</p>
<divclass="highlight-default notranslate"><divclass="highlight"><pre><span></span>$ sudo -H ./utils/filtron.sh remove all
$ sudo -H ./utils/morty.sh remove all
$ sudo -H ./utils/searx.sh remove all
</pre></div>
</div>
<divclass="admonition hint">
<pclass="admonition-title">Hint</p>
<p>If you are migrate from searx take into account that the <codeclass="docutils literal notranslate"><spanclass="pre">.config.sh</span></code> is no
longer used.</p>
</div>
<p>If you upgrade from searx or from before <aclass="extlink-pull reference external"href="https://github.com/searxng/searxng/pull/1332">PR 1332</a> has been merged and you
have filtron and/or morty installed, don’t forget to remove HTTP sites.</p>
<h3><aclass="toc-backref"href="#id7"role="doc-backlink">Check after Installation</a><aclass="headerlink"href="#check-after-installation"title="Link to this heading">¶</a></h3>
<p>Once you have done your installation, you can run a SearXNG <em>check</em> procedure,
to see if there are some left overs. In this example there exists a <em>old</em>