Rename all from searx to searxng

This commit is contained in:
HLFH 2021-09-29 11:26:25 +01:00
parent a582cf3d82
commit ac05f0943c
No known key found for this signature in database
GPG key ID: 200A60A75D394102
682 changed files with 58450 additions and 58450 deletions

View file

@ -6,7 +6,7 @@ Command Line Engines
.. sidebar:: info
- :origin:`command.py <searx/engines/command.py>`
- :origin:`command.py <searxng/engines/command.py>`
- :ref:`offline engines`
With *command engines* administrators can run engines to integrate arbitrary

View file

@ -35,7 +35,7 @@ Explanation of the :ref:`general engine configuration` shown in the table
Show errors **DE**
============= =========== =================================
.. jinja:: searx
.. jinja:: searxng
.. flat-table:: Engines configured at built time (defaults)
:header-rows: 1

View file

@ -20,4 +20,4 @@ Engines & Settings
nosql-engines
search-indexer-engines
command-line-engines
searx.engines.xpath
searxng.engines.xpath

View file

@ -14,17 +14,17 @@ The following `NoSQL databases`_ are supported:
- :ref:`engine mongodb`
All of the engines above are just commented out in the :origin:`settings.yml
<searx/settings.yml>`, as you have to set various options and install
<searxng/settings.yml>`, as you have to set various options and install
dependencies before using them.
By default, the engines use the ``key-value`` template for displaying results /
see :origin:`oscar <searx/templates/oscar/result_templates/key-value.html>` &
:origin:`simple <searx/templates/simple/result_templates/key-value.html>`
see :origin:`oscar <searxng/templates/oscar/result_templates/key-value.html>` &
:origin:`simple <searxng/templates/simple/result_templates/key-value.html>`
themes. If you are not satisfied with the original result layout, you can use
your own template, set ``result_template`` attribute to ``{template_name}`` and
place the templates at::
searx/templates/{theme_name}/result_templates/{template_name}
searxng/templates/{theme_name}/result_templates/{template_name}
Futhermore, if you do not wish to expose these engines on a public instance, you
can still add them and limit the access by setting ``tokens`` as described in
@ -43,11 +43,11 @@ Extra Dependencies
For using :ref:`engine redis_server` or :ref:`engine mongodb` you need to
install additional packages in Python's Virtual Environment of your SearXNG
instance. To switch into the environment (:ref:`searx-src`) you can use
:ref:`searx.sh`::
instance. To switch into the environment (:ref:`searxng-src`) you can use
:ref:`searxng.sh`::
$ sudo utils/searx.sh shell
(searx-pyenv)$ pip install ...
$ sudo utils/searxng.sh shell
(searxng-pyenv)$ pip install ...
.. _engine redis_server:
@ -61,7 +61,7 @@ Redis Server
- ``pip install`` redis_
- redis.io_
- :origin:`redis_server.py <searx/engines/redis_server.py>`
- :origin:`redis_server.py <searxng/engines/redis_server.py>`
Redis is an open source (BSD licensed), in-memory data structure (key value
@ -98,7 +98,7 @@ MongoDB
- ``pip install`` pymongo_
- MongoDB_
- :origin:`mongodb.py <searx/engines/mongodb.py>`
- :origin:`mongodb.py <searxng/engines/mongodb.py>`
MongoDB_ is a document based database program that handles JSON like data.
Before configuring the ``mongodb`` engine, you must install the dependency

View file

@ -8,7 +8,7 @@ Recoll Engine
- `Recoll <https://www.lesbonscomptes.com/recoll/>`_
- `recoll-webui <https://framagit.org/medoc92/recollwebui.git>`_
- :origin:`searx/engines/recoll.py`
- :origin:`searxng/engines/recoll.py`
Recoll_ is a desktop full-text search tool based on Xapian. By itself Recoll_
does not offer WEB or API access, this can be achieved using recoll-webui_

View file

@ -32,7 +32,7 @@ MeiliSearch
.. sidebar:: info
- :origin:`meilisearch.py <searx/engines/meilisearch.py>`
- :origin:`meilisearch.py <searxng/engines/meilisearch.py>`
- `MeiliSearch <https://www.meilisearch.com>`_
- `MeiliSearch Documentation <https://docs.meilisearch.com/>`_
- `Install MeiliSearch
@ -65,7 +65,7 @@ Elasticsearch
.. sidebar:: info
- :origin:`elasticsearch.py <searx/engines/elasticsearch.py>`
- :origin:`elasticsearch.py <searxng/engines/elasticsearch.py>`
- `Elasticsearch <https://www.elastic.co/elasticsearch/>`_
- `Elasticsearch Guide
<https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html>`_
@ -107,7 +107,7 @@ Solr
.. sidebar:: info
- :origin:`solr.py <searx/engines/solr.py>`
- :origin:`solr.py <searxng/engines/solr.py>`
- `Solr <https://solr.apache.org>`_
- `Solr Resources <https://solr.apache.org/resources.html>`_
- `Install Solr <https://solr.apache.org/guide/installing-solr.html>`_

View file

@ -4,6 +4,6 @@
XPath Engine
============
.. automodule:: searx.engines.xpath
.. automodule:: searxng.engines.xpath
:members:

View file

@ -4,7 +4,7 @@
``settings.yml``
================
This page describe the options possibilities of the :origin:`searx/settings.yml`
This page describe the options possibilities of the :origin:`searxng/settings.yml`
file.
.. sidebar:: Further reading ..
@ -24,11 +24,11 @@ settings.yml location
The initial ``settings.yml`` we be load from these locations:
1. the full path specified in the ``SEARX_SETTINGS_PATH`` environment variable.
2. ``/etc/searx/settings.yml``
1. the full path specified in the ``SEARXNG_SETTINGS_PATH`` environment variable.
2. ``/etc/searxng/settings.yml``
If these files don't exist (or are empty or can't be read), SearXNG uses the
:origin:`searx/settings.yml` file. Read :ref:`settings use_default_settings` to
:origin:`searxng/settings.yml` file. Read :ref:`settings use_default_settings` to
see how you can simplify your *user defined* ``settings.yml``.
@ -74,7 +74,7 @@ Global Settings
instance_name: "SearXNG" # displayed name
contact_url: false # mailto:contact@example.com
``debug`` : ``$SEARX_DEBUG``
``debug`` : ``$SEARXNG_DEBUG``
Allow a more detailed log if you run SearXNG directly. Display *detailed* error
messages in the browser too, so this must be deactivated in production.
@ -94,7 +94,7 @@ Global Settings
port: 8888
bind_address: "127.0.0.1" # address to listen on
secret_key: "ultrasecretkey" # change this!
image_proxy: false # proxying image results through searx
image_proxy: false # proxying image results through searxng
default_locale: "" # default interface locale
default_theme: oscar # ui theme
default_http_headers:
@ -109,17 +109,17 @@ Global Settings
Changing a value tagged by :ref:`buildenv <make buildenv>`, needs to
rebuild instance's environment :ref:`utils/brand.env <make buildenv>`.
``base_url`` : :ref:`buildenv SEARX_URL <make buildenv>`
``base_url`` : :ref:`buildenv SEARXNG_URL <make buildenv>`
The base URL where SearXNG is deployed. Used to create correct inbound links.
If you change the value, don't forget to rebuild instance's environment
(:ref:`utils/brand.env <make buildenv>`)
``port`` & ``bind_address``: :ref:`buildenv SEARX_PORT & SEARX_BIND_ADDRESS <make buildenv>`
``port`` & ``bind_address``: :ref:`buildenv SEARXNG_PORT & SEARXNG_BIND_ADDRESS <make buildenv>`
Port number and *bind address* of the SearXNG web application if you run it
directly using ``python searx/webapp.py``. Doesn't apply to SearXNG running on
directly using ``python searxng/webapp.py``. Doesn't apply to SearXNG running on
Apache or Nginx.
``secret_key`` : ``$SEARX_SECRET``
``secret_key`` : ``$SEARXNG_SECRET``
Used for cryptography purpose.
``image_proxy`` :
@ -128,7 +128,7 @@ Global Settings
``default_locale`` :
SearXNG interface language. If blank, the locale is detected by using the
browser language. If it doesn't work, or you are deploying a language
specific instance of searx, a locale can be defined using an ISO language
specific instance of searxng, a locale can be defined using an ISO language
code, like ``fr``, ``en``, ``de``.
``default_theme`` :
@ -137,7 +137,7 @@ Global Settings
.. _HTTP headers: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers
``default_http_headers``:
Set additional HTTP headers, see `#755 <https://github.com/searx/searx/issues/715>`__
Set additional HTTP headers, see `#755 <https://github.com/searxng/searxng/issues/715>`__
``outgoing:``
-------------
@ -293,7 +293,7 @@ engine is shown. Most of the options have a default value or even are optional.
``timeout`` : optional
Timeout of the search with the current search engine. **Be careful, it will
modify the global timeout of searx.**
modify the global timeout of searxng.**
``api_key`` : optional
In a few cases, using an API needs the use of a secret key. How to obtain them
@ -339,16 +339,16 @@ use_default_settings
- :ref:`settings location`
- :ref:`use_default_settings.yml`
- :origin:`/etc/searx/settings.yml <utils/templates/etc/searx/use_default_settings.yml>`
- :origin:`/etc/searxng/settings.yml <utils/templates/etc/searxng/use_default_settings.yml>`
The user defined ``settings.yml`` is loaded from the :ref:`settings location`
and can relied on the default configuration :origin:`searx/settings.yml` using:
and can relied on the default configuration :origin:`searxng/settings.yml` using:
``use_default_settings: true``
``server:``
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
in :origin:`searxng/settings.yml` with the exception of the ``secret_key`` and
the ``bind_address``:
.. code-block:: yaml

View file

@ -18,7 +18,7 @@ Relational Database Management System (RDBMS) are supported:
- :ref:`engine mysql_server`
All of the engines above are just commented out in the :origin:`settings.yml
<searx/settings.yml>`, as you have to set the required attributes for the
<searxng/settings.yml>`, as you have to set the required attributes for the
engines, e.g. ``database:`` ...
.. code:: yaml
@ -30,13 +30,13 @@ engines, e.g. ``database:`` ...
query_str: ...
By default, the engines use the ``key-value`` template for displaying results /
see :origin:`oscar <searx/templates/oscar/result_templates/key-value.html>` &
:origin:`simple <searx/templates/simple/result_templates/key-value.html>`
see :origin:`oscar <searxng/templates/oscar/result_templates/key-value.html>` &
:origin:`simple <searxng/templates/simple/result_templates/key-value.html>`
themes. If you are not satisfied with the original result layout, you can use
your own template, set ``result_template`` attribute to ``{template_name}`` and
place the templates at::
searx/templates/{theme_name}/result_templates/{template_name}
searxng/templates/{theme_name}/result_templates/{template_name}
If you do not wish to expose these engines on a public instance, you can still
add them and limit the access by setting ``tokens`` as described in section
@ -63,7 +63,7 @@ SQLite
.. sidebar:: info
- :origin:`sqlite.py <searx/engines/sqlite.py>`
- :origin:`sqlite.py <searxng/engines/sqlite.py>`
.. _MediathekView: https://mediathekview.de/
@ -74,7 +74,7 @@ this example of the SQlite engine download the database:
- https://liste.mediathekview.de/filmliste-v2.db.bz2
and unpack into ``searx/data/filmliste-v2.db``. To search the database use e.g
and unpack into ``searxng/data/filmliste-v2.db``. To search the database use e.g
Query to test: ``!mediathekview concert``
.. code:: yaml
@ -84,7 +84,7 @@ Query to test: ``!mediathekview concert``
disabled: False
categories: general
result_template: default.html
database: searx/data/filmliste-v2.db
database: searxng/data/filmliste-v2.db
query_str: >-
SELECT title || ' (' || time(duration, 'unixepoch') || ')' AS title,
COALESCE( NULLIF(url_video_hd,''), NULLIF(url_video_sd,''), url_video) AS url,
@ -99,11 +99,11 @@ Extra Dependencies
For using :ref:`engine postgresql` or :ref:`engine mysql_server` you need to
install additional packages in Python's Virtual Environment of your SearXNG
instance. To switch into the environment (:ref:`searx-src`) you can use
:ref:`searx.sh`::
instance. To switch into the environment (:ref:`searxng-src`) you can use
:ref:`searxng.sh`::
$ sudo utils/searx.sh shell
(searx-pyenv)$ pip install ...
$ sudo utils/searxng.sh shell
(searxng-pyenv)$ pip install ...
.. _engine postgresql:
@ -115,7 +115,7 @@ PostgreSQL
.. sidebar:: info
- :origin:`postgresql.py <searx/engines/postgresql.py>`
- :origin:`postgresql.py <searxng/engines/postgresql.py>`
- ``pip install`` psycopg2_
PostgreSQL is a powerful and robust open source database. Before configuring
@ -127,7 +127,7 @@ find an example configuration below:
- name: my_database
engine: postgresql
database: my_database
username: searx
username: searxng
password: password
query_str: 'SELECT * from my_table WHERE my_column = %(query)s'
@ -140,7 +140,7 @@ MySQL
.. sidebar:: info
- :origin:`mysql_server.py <searx/engines/mysql_server.py>`
- :origin:`mysql_server.py <searxng/engines/mysql_server.py>`
- ``pip install`` mysql-connector-python_
MySQL is said to be the most popular open source database. Before enabling MySQL
@ -155,7 +155,7 @@ example configuration for quering a MySQL server:
- name: my_database
engine: mysql_server
database: my_database
username: searx
username: searxng
password: password
limit: 5
query_str: 'SELECT * from my_table WHERE my_column=%(query)s'