mirror of
https://github.com/parchlinuxB/Gitee.git
synced 2025-02-23 02:15:43 -05:00
edfbf1e118
Typification of SearXNG
=======================
This patch introduces the typing of the results. The why and how is described
in the documentation, please generate the documentation ..
$ make docs.clean docs.live
and read the following articles in the "Developer documentation":
- result types --> http://0.0.0.0:8000/dev/result_types/index.html
The result types are available from the `searx.result_types` module. The
following have been implemented so far:
- base result type: `searx.result_type.Result`
--> http://0.0.0.0:8000/dev/result_types/base_result.html
- answer results
--> http://0.0.0.0:8000/dev/result_types/answer.html
including the type for translations (inspired by #3925). For all other
types (which still need to be set up in subsequent PRs), template documentation
has been created for the transition period.
Doc of the fields used in Templates
===================================
The template documentation is the basis for the typing and is the first complete
documentation of the results (needed for engine development). It is the
"working paper" (the plan) with which further typifications can be implemented
in subsequent PRs.
- https://github.com/searxng/searxng/issues/357
Answer Templates
================
With the new (sub) types for `Answer`, the templates for the answers have also
been revised, `Translation` are now displayed with collapsible entries (inspired
by #3925).
!en-de dog
Plugins & Answerer
==================
The implementation for `Plugin` and `Answer` has been revised, see
documentation:
- Plugin: http://0.0.0.0:8000/dev/plugins/index.html
- Answerer: http://0.0.0.0:8000/dev/answerers/index.html
With `AnswerStorage` and `AnswerStorage` to manage those items (in follow up
PRs, `ArticleStorage`, `InfoStorage` and .. will be implemented)
Autocomplete
============
The autocompletion had a bug where the results from `Answer` had not been shown
in the past. To test activate autocompletion and try search terms for which we
have answerers
- statistics: type `min 1 2 3` .. in the completion list you should find an
entry like `[de] min(1, 2, 3) = 1`
- random: type `random uuid` .. in the completion list, the first item is a
random UUID
Extended Types
==============
SearXNG extends e.g. the request and response types of flask and httpx, a module
has been set up for type extensions:
- Extended Types
--> http://0.0.0.0:8000/dev/extended_types.html
Unit-Tests
==========
The unit tests have been completely revised. In the previous implementation,
the runtime (the global variables such as `searx.settings`) was not initialized
before each test, so the runtime environment with which a test ran was always
determined by the tests that ran before it. This was also the reason why we
sometimes had to observe non-deterministic errors in the tests in the past:
- https://github.com/searxng/searxng/issues/2988 is one example for the Runtime
issues, with non-deterministic behavior ..
- https://github.com/searxng/searxng/pull/3650
- https://github.com/searxng/searxng/pull/3654
- https://github.com/searxng/searxng/pull/3642#issuecomment-2226884469
- https://github.com/searxng/searxng/pull/3746#issuecomment-2300965005
Why msgspec.Struct
==================
We have already discussed typing based on e.g. `TypeDict` or `dataclass` in the past:
- https://github.com/searxng/searxng/pull/1562/files
- https://gist.github.com/dalf/972eb05e7a9bee161487132a7de244d2
- https://github.com/searxng/searxng/pull/1412/files
- https://github.com/searxng/searxng/pull/1356
In my opinion, TypeDict is unsuitable because the objects are still dictionaries
and not instances of classes / the `dataclass` are classes but ...
The `msgspec.Struct` combine the advantages of typing, runtime behaviour and
also offer the option of (fast) serializing (incl. type check) the objects.
Currently not possible but conceivable with `msgspec`: Outsourcing the engines
into separate processes, what possibilities this opens up in the future is left
to the imagination!
Internally, we have already defined that it is desirable to decouple the
development of the engines from the development of the SearXNG core / The
serialization of the `Result` objects is a prerequisite for this.
HINT: The threads listed above were the template for this PR, even though the
implementation here is based on msgspec. They should also be an inspiration for
the following PRs of typification, as the models and implementations can provide
a good direction.
Why just one commit?
====================
I tried to create several (thematically separated) commits, but gave up at some
point ... there are too many things to tackle at once / The comprehensibility of
the commits would not be improved by a thematic separation. On the contrary, we
would have to make multiple changes at the same places and the goal of a change
would be vaguely recognizable in the fog of the commits.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
254 lines
11 KiB
ReStructuredText
254 lines
11 KiB
ReStructuredText
.. _engines-dev:
|
|
|
|
===============
|
|
Engine Overview
|
|
===============
|
|
|
|
.. contents::
|
|
:depth: 3
|
|
:local:
|
|
:backlinks: entry
|
|
|
|
.. _metasearch-engine: https://en.wikipedia.org/wiki/Metasearch_engine
|
|
|
|
.. sidebar:: Further reading ..
|
|
|
|
- :ref:`configured engines`
|
|
- :ref:`settings engine`
|
|
|
|
SearXNG is a metasearch-engine_, so it uses different search engines to provide
|
|
better results.
|
|
|
|
Because there is no general search API which could be used for every search
|
|
engine, an adapter has to be built between SearXNG and the external search
|
|
engines. Adapters are stored under the folder :origin:`searx/engines`.
|
|
|
|
.. _general engine configuration:
|
|
|
|
General Engine Configuration
|
|
============================
|
|
|
|
It is required to tell SearXNG the type of results the engine provides. The
|
|
arguments can be set in the engine file or in the settings file (normally
|
|
``settings.yml``). The arguments in the settings file override the ones in the
|
|
engine file.
|
|
|
|
It does not matter if an option is stored in the engine file or in the settings.
|
|
However, the standard way is the following:
|
|
|
|
.. _engine file:
|
|
|
|
Engine File
|
|
-----------
|
|
|
|
.. table:: Common options in the engine module
|
|
:width: 100%
|
|
|
|
======================= =========== ========================================================
|
|
argument type information
|
|
======================= =========== ========================================================
|
|
categories list categories, in which the engine is working
|
|
paging boolean support multiple pages
|
|
time_range_support boolean support search time range
|
|
engine_type str - ``online`` :ref:`[ref] <online engines>` by
|
|
default, other possibles values are:
|
|
- ``offline`` :ref:`[ref] <offline engines>`
|
|
- ``online_dictionary`` :ref:`[ref] <online dictionary>`
|
|
- ``online_currency`` :ref:`[ref] <online currency>`
|
|
- ``online_url_search`` :ref:`[ref] <online url search>`
|
|
======================= =========== ========================================================
|
|
|
|
.. _engine settings:
|
|
|
|
Engine ``settings.yml``
|
|
-----------------------
|
|
|
|
For a more detailed description, see :ref:`settings engine` in the :ref:`settings.yml`.
|
|
|
|
.. table:: Common options in the engine setup (``settings.yml``)
|
|
:width: 100%
|
|
|
|
======================= =========== ==================================================
|
|
argument type information
|
|
======================= =========== ==================================================
|
|
name string name of search-engine
|
|
engine string name of searxng-engine (file name without ``.py``)
|
|
enable_http bool enable HTTP (by default only HTTPS is enabled).
|
|
shortcut string shortcut of search-engine
|
|
timeout string specific timeout for search-engine
|
|
display_error_messages boolean display error messages on the web UI
|
|
proxies dict set proxies for a specific engine
|
|
(e.g. ``proxies : {http: socks5://proxy:port,
|
|
https: socks5://proxy:port}``)
|
|
======================= =========== ==================================================
|
|
|
|
.. _engine overrides:
|
|
|
|
Overrides
|
|
---------
|
|
|
|
A few of the options have default values in the namespace of the engine's python
|
|
module, but are often overwritten by the settings. If ``None`` is assigned to an
|
|
option in the engine file, it has to be redefined in the settings, otherwise
|
|
SearXNG will not start with that engine (global names with a leading underline can
|
|
be ``None``).
|
|
|
|
Here is an very simple example of the global names in the namespace of engine's
|
|
module:
|
|
|
|
.. code:: python
|
|
|
|
# engine dependent config
|
|
categories = ['general']
|
|
paging = True
|
|
_non_overwritten_global = 'foo'
|
|
|
|
|
|
.. table:: The naming of overrides is arbitrary / recommended overrides are:
|
|
:width: 100%
|
|
|
|
======================= =========== ===========================================
|
|
argument type information
|
|
======================= =========== ===========================================
|
|
base_url string base-url, can be overwritten to use same
|
|
engine on other URL
|
|
number_of_results int maximum number of results per request
|
|
language string ISO code of language and country like en_US
|
|
api_key string api-key if required by engine
|
|
======================= =========== ===========================================
|
|
|
|
.. _engine request:
|
|
|
|
Making a Request
|
|
================
|
|
|
|
To perform a search an URL have to be specified. In addition to specifying an
|
|
URL, arguments can be passed to the query.
|
|
|
|
.. _engine request arguments:
|
|
|
|
Passed Arguments (request)
|
|
--------------------------
|
|
|
|
These arguments can be used to construct the search query. Furthermore,
|
|
parameters with default value can be redefined for special purposes.
|
|
|
|
.. _engine request online:
|
|
|
|
.. table:: If the ``engine_type`` is :py:obj:`online
|
|
<searx.search.processors.online.OnlineProcessor.get_params>`
|
|
:width: 100%
|
|
|
|
====================== ============== ========================================================================
|
|
argument type default-value, information
|
|
====================== ============== ========================================================================
|
|
url str ``''``
|
|
method str ``'GET'``
|
|
headers set ``{}``
|
|
data set ``{}``
|
|
cookies set ``{}``
|
|
verify bool ``True``
|
|
headers.User-Agent str a random User-Agent
|
|
category str current category, like ``'general'``
|
|
safesearch int ``0``, between ``0`` and ``2`` (normal, moderate, strict)
|
|
time_range Optional[str] ``None``, can be ``day``, ``week``, ``month``, ``year``
|
|
pageno int current pagenumber
|
|
searxng_locale str SearXNG's locale selected by user. Specific language code like
|
|
``'en'``, ``'en-US'``, or ``'all'`` if unspecified.
|
|
====================== ============== ========================================================================
|
|
|
|
|
|
.. _engine request online_dictionary:
|
|
|
|
.. table:: If the ``engine_type`` is :py:obj:`online_dictionary
|
|
<searx.search.processors.online_dictionary.OnlineDictionaryProcessor.get_params>`,
|
|
in addition to the :ref:`online <engine request online>` arguments:
|
|
:width: 100%
|
|
|
|
====================== ============== ========================================================================
|
|
argument type default-value, information
|
|
====================== ============== ========================================================================
|
|
from_lang str specific language code like ``'en_US'``
|
|
to_lang str specific language code like ``'en_US'``
|
|
query str the text query without the languages
|
|
====================== ============== ========================================================================
|
|
|
|
.. _engine request online_currency:
|
|
|
|
.. table:: If the ``engine_type`` is :py:obj:`online_currency
|
|
<searx.search.processors.online_currency.OnlineCurrencyProcessor.get_params>`,
|
|
in addition to the :ref:`online <engine request online>` arguments:
|
|
:width: 100%
|
|
|
|
====================== ============== ========================================================================
|
|
argument type default-value, information
|
|
====================== ============== ========================================================================
|
|
amount float the amount to convert
|
|
from str ISO 4217 code
|
|
to str ISO 4217 code
|
|
from_name str currency name
|
|
to_name str currency name
|
|
====================== ============== ========================================================================
|
|
|
|
.. _engine request online_url_search:
|
|
|
|
.. table:: If the ``engine_type`` is :py:obj:`online_url_search
|
|
<searx.search.processors.online_url_search.OnlineUrlSearchProcessor.get_params>`,
|
|
in addition to the :ref:`online <engine request online>` arguments:
|
|
:width: 100%
|
|
|
|
====================== ============== ========================================================================
|
|
argument type default-value, information
|
|
====================== ============== ========================================================================
|
|
search_url dict URLs from the search query:
|
|
|
|
.. code:: python
|
|
|
|
{
|
|
'http': str,
|
|
'ftp': str,
|
|
'data:image': str
|
|
}
|
|
====================== ============== ========================================================================
|
|
|
|
Specify Request
|
|
---------------
|
|
|
|
The function :py:func:`def request(query, params):
|
|
<searx.engines.demo_online.request>` always returns the ``params`` variable, the
|
|
following parameters can be used to specify a search request:
|
|
|
|
.. table::
|
|
:width: 100%
|
|
|
|
=================== =========== ==========================================================================
|
|
argument type information
|
|
=================== =========== ==========================================================================
|
|
url str requested url
|
|
method str HTTP request method
|
|
headers set HTTP header information
|
|
data set HTTP data information
|
|
cookies set HTTP cookies
|
|
verify bool Performing SSL-Validity check
|
|
allow_redirects bool Follow redirects
|
|
max_redirects int maximum redirects, hard limit
|
|
soft_max_redirects int maximum redirects, soft limit. Record an error but don't stop the engine
|
|
raise_for_httperror bool True by default: raise an exception if the HTTP code of response is >= 300
|
|
=================== =========== ==========================================================================
|
|
|
|
|
|
Making a Response
|
|
=================
|
|
|
|
In the ``response`` function of the engine, the HTTP response (``resp``) is
|
|
parsed and a list of results is returned.
|
|
|
|
A engine can append result-items of different media-types and different
|
|
result-types to the result list. The list of the result items is render to HTML
|
|
by templates. For more details read section:
|
|
|
|
- :ref:`simple theme templates`
|
|
- :ref:`result types`
|
|
|
|
|
|
|