@@ -27,7 +27,8 @@ First, searx will try to load settings.yml from these locations:
271. the full path specified in the ``SEARX_SETTINGS_PATH`` environment variable.
271. the full path specified in the ``SEARX_SETTINGS_PATH`` environment variable.
282. ``/etc/searx/settings.yml``
282. ``/etc/searx/settings.yml``
30−If these files don't exist (or are empty or can't be read), searx uses the :origin:`searx/settings.yml` file.
30+If these files don't exist (or are empty or can't be read), searx uses the
31+:origin:`searx/settings.yml` file.
33.. _settings global:
34.. _settings global:
@@ -35,16 +36,46 @@ If these files don't exist (or are empty or can't be read), searx uses the :orig
35Global Settings
36Global Settings
36===============
37===============
38.. code:: yaml
42.. code:: yaml
41 debug : False # Debug mode, only for development
45 debug : False # Debug mode, only for development
42 instance_name : "searx" # displayed name
46 instance_name : "searx" # displayed name
47+ git_url: https://github.com/searx/searx
49+ issue_url: https://github.com/searx/searx/issues
50+ docs_url: https://searx.github.io/searx
51+ public_instances: https://searx.space
52+ contact_url: False # mailto:contact@example.com
53+ wiki_url: https://github.com/searx/searx/wiki
54+ twitter_url: https://twitter.com/Searx_engine
44``debug`` :
56``debug`` :
45 Allow a more detailed log if you run searx directly. Display *detailed* error
57 Allow a more detailed log if you run searx directly. Display *detailed* error
46 messages in the browser too, so this must be deactivated in production.
58 messages in the browser too, so this must be deactivated in production.
61+ Contact ``mailto:`` address or WEB form.
63+``git_url`` and ``git_branch``:
64+ Changes this, to point to your searx fork (branch).
67+ If you host your own documentation, change this URL.
70+ Link to your wiki (or ``False``)
73+ Link to your tweets (or ``False``)
48.. code:: yaml
79.. code:: yaml
@@ -90,6 +121,8 @@ Global Settings
90``default_http_headers``:
121``default_http_headers``:
91 Set additional HTTP headers, see `#755 <https://github.com/searx/searx/issues/715>`__
122 Set additional HTTP headers, see `#755 <https://github.com/searx/searx/issues/715>`__
94.. code:: yaml
127.. code:: yaml
@@ -139,6 +172,10 @@ Global Settings
139 If you use multiple network interfaces, define from which IP the requests must
172 If you use multiple network interfaces, define from which IP the requests must
140 be made. This parameter is ignored when ``proxies`` is set.
173 be made. This parameter is ignored when ``proxies`` is set.
142.. code:: yaml
179.. code:: yaml
@@ -244,61 +281,76 @@ Engine settings
244use_default_settings
281use_default_settings
245====================
282====================
247−.. note::
284+.. sidebar:: ``use_default_settings: True``
249− If searx is cloned from a git repository, most probably there is no need to have an user settings.
251−The user defined settings.yml can relied on the default configuration :origin:`searx/settings.yml` using ``use_default_settings: True``.
286+ - :ref:`settings location`
287+ - :ref:`use_default_settings.yml`
288+ - :origin:`/etc/searx/settings.yml <utils/templates/etc/searx/use_default_settings.yml>`
290+The user defined ``settings.yml`` is loaded from the :ref:`settings location`
291+and can relied on the default configuration :origin:`searx/settings.yml` using:
293+ ``use_default_settings: True``
253−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``:
296+ In the following example, the actual settings are the default settings defined
254−
297+ in :origin:`searx/settings.yml` with the exception of the ``secret_key`` and
298+ the ``bind_address``:
255−.. code-block:: yaml
300+ .. code-block:: yaml
257− use_default_settings: True
302+ use_default_settings: True
259− secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
304+ secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
260− bind_address: "0.0.0.0"
305+ bind_address: "0.0.0.0"
262−With ``use_default_settings: True``, each settings can be override in a similar way, the ``engines`` section is merged according to the engine ``name``.
308+ With ``use_default_settings: True``, each settings can be override in a
263−
309+ similar way, the ``engines`` section is merged according to the engine
264−In this example, searx will load all the engine and the arch linux wiki engine has a :ref:`token<private engines>`:
310+ ``name``. In this example, searx will load all the engine and the arch linux
265−
311+ wiki engine has a :ref:`token<private engines>`:
266−.. code-block:: yaml
313+ .. code-block:: yaml
268− use_default_settings: True
315+ use_default_settings: True
270− secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
317+ secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
271− engines:
318+ engines:
272− - name: arch linux wiki
319+ - name: arch linux wiki
273− tokens: ['$ecretValue']
320+ tokens: ['$ecretValue']
322+``engines:`` / ``remove:``
275−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:
323+ It is possible to remove some engines from the default settings. The following
276−
324+ example is similar to the above one, but searx doesn't load the the google
277−.. code-block:: yaml
327+ .. code-block:: yaml
279− use_default_settings:
329+ use_default_settings:
280− engines:
330+ engines:
282− - google
332+ - google
284− secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
334+ secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
285− engines:
335+ engines:
286− - name: arch linux wiki
336+ - name: arch linux wiki
287− tokens: ['$ecretValue']
337+ tokens: ['$ecretValue']
339+``engines:`` / ``keep_only:``
289−As an alternative, it is possible to specify the engines to keep. In the following example, searx has only two engines:
340+ As an alternative, it is possible to specify the engines to keep. In the
290−
341+ following example, searx has only two engines:
291−.. code-block:: yaml
343+ .. code-block:: yaml
293− use_default_settings:
345+ use_default_settings:
294− engines:
346+ engines:
295− keep_only:
347+ keep_only:
296− - google
348+ - google
297− - duckduckgo
349+ - duckduckgo
299− secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
351+ secret_key: "uvys6bRhKHUdFF5CqbJonSDSRN8H0sCBziNSrDGNVdpz7IeZhveVart3yvghoKHA"
300− engines:
352+ engines:
301− - name: google
353+ - name: google
302− tokens: ['$ecretValue']
354+ tokens: ['$ecretValue']
303− - name: duckduckgo
355+ - name: duckduckgo
304− tokens: ['$ecretValue']
356+ tokens: ['$ecretValue']