mirror of
https://github.com/searxng/searxng.git
synced 2025-07-16 09:49:21 +02:00
574b285efa
Cache busting has caused serious problems for users in the past, here are two examples: - https://github.com/searxng/searxng/issues/4419 - https://github.com/searxng/searxng/issues/4481 And it makes development and deployment significantly more complex because it binds the client side to the server side: - https://github.com/searxng/searxng/pull/4466 In the light of a decoupled development of the WEB clients from the server side: - https://github.com/searxng/searxng/pull/4988 is it appropriate to abandon this feature. In fact, it has been ineffective since #4436 anyway. However, the benefit has always been questionable, since at best only a few kB of data are saved (at least in the context of an image_proxy, the effect is below the detection limit). Ultimately, the client is responsible for caching. Related: https://github.com/searxng/searxng/issues?q=label%3A%22clear%20browser%20cache%22 Closes: https://github.com/searxng/searxng/pull/4466 Closes: https://github.com/searxng/searxng/issues/1326 Closes: https://github.com/searxng/searxng/issues/964 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
89 lines
2.5 KiB
ReStructuredText
89 lines
2.5 KiB
ReStructuredText
.. _searxng maintenance:
|
|
|
|
===================
|
|
SearXNG maintenance
|
|
===================
|
|
|
|
.. sidebar:: further read
|
|
|
|
- :ref:`toolboxing`
|
|
- :ref:`uWSGI maintenance`
|
|
|
|
.. contents::
|
|
:depth: 2
|
|
:local:
|
|
:backlinks: entry
|
|
|
|
.. _update searxng:
|
|
|
|
How to update
|
|
=============
|
|
|
|
How to update depends on the :ref:`installation` method. If you have used the
|
|
:ref:`installation scripts`, use the ``update`` command from the :ref:`searxng.sh`
|
|
script.
|
|
|
|
.. code:: sh
|
|
|
|
sudo -H ./utils/searxng.sh instance update
|
|
|
|
.. _inspect searxng:
|
|
|
|
How to inspect & debug
|
|
======================
|
|
|
|
How to debug depends on the :ref:`installation` method. If you have used the
|
|
:ref:`installation scripts`, use the ``inspect`` command from the :ref:`searxng.sh`
|
|
script.
|
|
|
|
.. code:: sh
|
|
|
|
sudo -H ./utils/searxng.sh instance inspect
|
|
|
|
.. _migrate and stay tuned:
|
|
|
|
Migrate and stay tuned!
|
|
=======================
|
|
|
|
.. sidebar:: info
|
|
|
|
- :pull:`1332`
|
|
- :pull:`456`
|
|
- :pull:`A comment about rolling release <446#issuecomment-954730358>`
|
|
|
|
SearXNG is a *rolling release*; 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:
|
|
|
|
- Bot protection has been switched from filtron to SearXNG's :ref:`limiter
|
|
<limiter>`, this requires a :ref:`Valkey <settings valkey>` database.
|
|
|
|
To stay tuned and get in use of the new features, instance maintainers have to
|
|
update the SearXNG code regularly (see :ref:`update searxng`). 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.
|
|
|
|
Here you will find a list of changes that affect the infrastructure. Please
|
|
check to what extent it is necessary to update your installations:
|
|
|
|
:pull:`1595`: ``[fix] uWSGI: increase buffer-size``
|
|
Re-install uWSGI (:ref:`searxng.sh`) or fix your uWSGI ``searxng.ini``
|
|
file manually.
|
|
|
|
|
|
Check after Installation
|
|
------------------------
|
|
|
|
Once you have done your installation, you can run a SearXNG *check* procedure,
|
|
to see if there are some left overs. In this example there exists a *old*
|
|
``/etc/searx/settings.yml``::
|
|
|
|
$ sudo -H ./utils/searxng.sh instance check
|
|
|
|
SearXNG checks
|
|
--------------
|
|
ERROR: settings.yml in /etc/searx/ is deprecated, move file to folder /etc/searxng/
|
|
...
|
|
INFO searx.valkeydb : connecting to Valkey db=0 path='/usr/local/searxng-valkey/run/valkey.sock'
|
|
INFO searx.valkeydb : connected to Valkey
|