@ -27,7 +27,8 @@ First, searx will try to load settings.yml from these locations:
1. the full path specified in the ``SEARX_SETTINGS_PATH`` environment variable.
2. ``/etc/searx/settings.yml``
If these files don't exist (or are empty or can't be read), searx uses the :origin:`searx/settings.yml` file.
If these files don't exist (or are empty or can't be read), searx uses the
:origin:`searx/settings.yml` file.
.._settings global:
@ -35,6 +36,9 @@ If these files don't exist (or are empty or can't be read), searx uses the :orig
Global Settings
===============
``general:``
------------
..code:: yaml
general:
@ -54,7 +58,7 @@ Global Settings
messages in the browser too, so this must be deactivated in production.
``contact_url``:
Contact mail address or WEB form.
Contact ``mailto:`` address or WEB form.
``git_url`` and ``git_branch``:
Changes this, to point to your searx fork (branch).
@ -69,6 +73,9 @@ Global Settings
Link to your tweets (or ``False``)
``server:``
-----------
..code:: yaml
server:
@ -114,6 +121,8 @@ Global Settings
``default_http_headers``:
Set additional HTTP headers, see `#755 <https://github.com/searx/searx/issues/715>`__
``outgoing:``
-------------
..code:: yaml
@ -163,6 +172,10 @@ Global Settings
If you use multiple network interfaces, define from which IP the requests must
be made. This parameter is ignored when ``proxies`` is set.
``locales:``
------------
..code:: yaml
locales:
@ -268,61 +281,76 @@ Engine settings
use_default_settings
====================
..note::
If searx is cloned from a git repository, most probably there is no need to have an user settings.
The user defined settings.yml can relied on the default configuration :origin:`searx/settings.yml` using ``use_default_settings: True``.
In the following example, the actual settings are the default settings defined in :origin:`searx/settings.yml` with the exception of the ``secret_key`` and the ``bind_address``:
With ``use_default_settings: True``, each settings can be override in a similar way, the ``engines`` section is merged according to the engine ``name``.
In this example, searx will load all the engine and the arch linux wiki engine has a :ref:`token<private engines>`:
It is possible to remove some engines from the default settings. The following example is similar to the above one, but searx doesn't load the the google engine: