mirror of
https://github.com/searxng/searxng.git
synced 2025-11-03 19:17:07 -05: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>
39 lines
974 B
ReStructuredText
39 lines
974 B
ReStructuredText
.. _architecture:
|
|
|
|
============
|
|
Architecture
|
|
============
|
|
|
|
.. sidebar:: Further reading
|
|
|
|
- Reverse Proxy: :ref:`Apache <apache searxng site>` & :ref:`nginx <nginx
|
|
searxng site>`
|
|
- uWSGI: :ref:`searxng uwsgi`
|
|
- SearXNG: :ref:`installation basic`
|
|
|
|
Herein you will find some hints and suggestions about typical architectures of
|
|
SearXNG infrastructures.
|
|
|
|
.. _architecture uWSGI:
|
|
|
|
uWSGI Setup
|
|
===========
|
|
|
|
We start with a *reference* setup for public SearXNG instances which can be build
|
|
up and maintained by the scripts from our :ref:`toolboxing`.
|
|
|
|
.. _arch public:
|
|
|
|
.. kernel-figure:: arch_public.dot
|
|
:alt: arch_public.dot
|
|
|
|
Reference architecture of a public SearXNG setup.
|
|
|
|
The reference installation activates ``server.limiter`` and
|
|
``server.image_proxy`` (:origin:`/etc/searxng/settings.yml
|
|
<utils/templates/etc/searxng/settings.yml>`)
|
|
|
|
.. literalinclude:: ../../utils/templates/etc/searxng/settings.yml
|
|
:language: yaml
|
|
:end-before: # preferences:
|