Previously, with searx you could search over the Internet on other people's
..sidebar:: info
computers. Now it is possible to fetch results from your local machine without
connecting to any networks from the same graphical user interface.
.._command line engines:
- :origin:`command.py <searx/engines/command.py>`
- :ref:`offline engines`
Command line engines
With *command engines* administrators can run engines to integrate arbitrary
====================
shell commands.
When creating and enabling a ``command`` engine on a public instance, you must
be careful to avoid leaking private data. The easiest solution is to limit the
access by setting ``tokens`` as described in section :ref:`private engines`.
The engine base is flexible. Only your imagination can limit the power of this
engine (and maybe security concerns). The following options are available:
``command``:
A comma separated list of the elements of the command. A special token
``{{QUERY}}`` tells where to put the search terms of the user. Example:
..code:: yaml
['ls', '-l', '-h', '{{QUERY}}']
``delimiter``:
A mapping containing a delimiter ``char`` and the *titles* of each element in
``keys``.
In :pull-searx:`2128` a new type of engine has been introduced called ``command``.
``parse_regex``:
This engine lets administrators add engines which run arbitrary shell commands
A dict containing the regular expressions for each result key.
and show its output on the web UI of searx.
When creating and enabling a ``command`` engine on a public searx instance,
``query_type``:
you must be careful to avoid leaking private data. The easiest solution
is to add tokens to the engine. Thus, only those who have the appropriate token
can retrieve results from the it.
The engine base is flexible. Only your imagination can limit the power of this engine. (And
The expected type of user search terms. Possible values: ``path`` and
maybe security concerns.) The following options are available:
``enum``.
* ``command``: A comma separated list of the elements of the command. A special token {{QUERY}} tells searx where to put the search terms of the user. Example: ``['ls', '-l', '-h', '{{QUERY}}']``
``path``:
* ``delimiter``: A dict containing a delimiter char and the "titles" of each element in keys.
Checks if the user provided path is inside the working directory. If not,
* ``parse_regex``: A dict containing the regular expressions for each result key.
the query is not executed.
* ``query_type``: The expected type of user search terms. Possible values: ``path`` and ``enum``. ``path`` checks if the uesr provided path is inside the working directory. If not the query is not executed. ``enum`` is a list of allowed search terms. If the user submits something which is not included in the list, the query returns an error.
* ``query_enum``: A list containing allowed search terms if ``query_type`` is set to ``enum``.
* ``working_dir``: The directory where the command has to be executed. Default: ``.``
* ``result_separator``: The character that separates results. Default: ``\n``
The example engine below can be used to find files with a specific name in the configured
``enum``:
working directory.
Is a list of allowed search terms. If the user submits something which is
not included in the list, the query returns an error.
``query_enum``:
A list containing allowed search terms if ``query_type`` is set to ``enum``.
``working_dir``:
The directory where the command has to be executed. Default: ``./``
``result_separator``:
The character that separates results. Default: ``\n``
The example engine below can be used to find files with a specific name in the
configured working directory:
..code:: yaml
..code:: yaml
@ -49,16 +72,8 @@ working directory.
keys: ['line']
keys: ['line']
Next steps
Acknowledgment
==========
==============
In the next milestone, support for local search engines and indexers (e.g. Elasticsearch)
are going to be added. This way, you will be able to query your own databases/indexers.
Acknowledgement
===============
This development was sponsored by `Search and Discovery Fund`_ of `NLnet Foundation`_ .
.._Search and Discovery Fund: https://nlnet.nl/discovery
This development was sponsored by `Search and Discovery Fund
.._NLnet Foundation: https://nlnet.nl/
<https://nlnet.nl/discovery>`_ of `NLnet Foundation <https://nlnet.nl/>`_.
Markus Heiser
3 years ago