forked from zaclys/searxng
fix: minor typos
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
This commit is contained in:
parent
857a1458b1
commit
c15337850e
|
@ -18,7 +18,7 @@ How to protect an instance
|
|||
|
||||
.. _filtron: https://github.com/asciimoo/filtron
|
||||
|
||||
Searx depens on external search services. To avoid the abuse of these services
|
||||
Searx depends on external search services. To avoid the abuse of these services
|
||||
it is advised to limit the number of requests processed by searx.
|
||||
|
||||
An application firewall, filtron_ solves exactly this problem. Filtron is just
|
||||
|
|
|
@ -186,7 +186,7 @@ Started wiki`_ is always a good resource *to keep in the pocket*.
|
|||
|
||||
.. group-tab:: proxy or uWSGI
|
||||
|
||||
Be warned, with this setup, your Instance isn't :ref:`protected <searx
|
||||
Be warned, with this setup, your instance isn't :ref:`protected <searx
|
||||
filtron>`. Nevertheless it is good enough for intranet usage and it is a
|
||||
excellent example of; *how different services can be set up*. The next
|
||||
example shows a reverse proxy configuration wrapping the :ref:`searx-uWSGI
|
||||
|
@ -246,7 +246,7 @@ Started wiki`_ is always a good resource *to keep in the pocket*.
|
|||
|
||||
.. group-tab:: subdirectory URL
|
||||
|
||||
Be warned, with these setups, your Instance isn't :ref:`protected <searx
|
||||
Be warned, with these setups, your instance isn't :ref:`protected <searx
|
||||
filtron>`. The examples are just here to demonstrate how to export the
|
||||
searx application from a subdirectory URL ``https://example.org/searx/``.
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ env = SEARX_SETTINGS_PATH=${SEARX_SETTINGS_PATH}
|
|||
|
||||
# disable logging for privacy
|
||||
logger = systemd
|
||||
disable-logging = false
|
||||
disable-logging = true
|
||||
|
||||
# The right granted on the created socket
|
||||
chmod-socket = 666
|
||||
|
|
Loading…
Reference in New Issue