2019-12-30 18:31:17 +01:00
|
|
|
.. _architecture:
|
|
|
|
|
|
|
|
|
|
============
|
|
|
|
|
Architecture
|
|
|
|
|
============
|
|
|
|
|
|
2020-04-19 12:57:50 +02:00
|
|
|
.. sidebar:: Needs work!
|
2019-12-30 18:31:17 +01:00
|
|
|
|
2020-04-19 12:57:50 +02:00
|
|
|
This article needs some work / Searx is a collaborative effort. If you have
|
|
|
|
|
any contribution, feel welcome to send us your :pull:`PR <../pulls>`, see
|
|
|
|
|
:ref:`how to contribute`.
|
2019-12-30 18:31:17 +01:00
|
|
|
|
|
|
|
|
Herein you will find some hints and suggestions about typical architectures of
|
|
|
|
|
searx infrastructures.
|
|
|
|
|
|
|
|
|
|
We start with a contribution from :pull:`@dalf <1776#issuecomment-567917320>`.
|
2020-04-19 12:57:50 +02:00
|
|
|
It shows a *reference* setup for public searx instances.
|
2019-12-30 18:31:17 +01:00
|
|
|
|
|
|
|
|
.. _arch public:
|
|
|
|
|
|
|
|
|
|
.. kernel-figure:: arch_public.dot
|
|
|
|
|
:alt: arch_public.dot
|
|
|
|
|
|
|
|
|
|
Reference architecture of a public searx setup.
|
