2020-06-19 11:15:15 +02:00
|
|
|
|
|
|
|
|
.. _searx morty:
|
|
|
|
|
|
2019-12-30 18:31:17 +01:00
|
|
|
=========================
|
|
|
|
|
How to setup result proxy
|
|
|
|
|
=========================
|
|
|
|
|
|
2020-06-19 11:15:15 +02:00
|
|
|
.. sidebar:: further reading
|
|
|
|
|
|
|
|
|
|
- :ref:`morty.sh`
|
|
|
|
|
|
2019-12-30 18:31:17 +01:00
|
|
|
.. _morty: https://github.com/asciimoo/morty
|
|
|
|
|
.. _morty's README: https://github.com/asciimoo/morty
|
|
|
|
|
|
|
|
|
|
By default searx can only act as an image proxy for result images, but it is
|
|
|
|
|
possible to proxify all the result URLs with an external service, morty_.
|
|
|
|
|
|
|
|
|
|
To use this feature, morty has to be installed and activated in searx's
|
2021-01-27 15:34:25 +01:00
|
|
|
``settings.yml``. Add the following snippet to your ``settings.yml`` and
|
|
|
|
|
restart searx:
|
2019-12-30 18:31:17 +01:00
|
|
|
|
|
|
|
|
.. code:: yaml
|
|
|
|
|
|
|
|
|
|
result_proxy:
|
|
|
|
|
url : http://127.0.0.1:3000/
|
2021-01-27 15:34:25 +01:00
|
|
|
key : !!binary "insert_your_morty_proxy_key_here"
|
|
|
|
|
|
|
|
|
|
Note that the example above (``http://127.0.0.1:3000``) is only for single-user
|
|
|
|
|
instances without a HTTP proxy. If your morty service is public, the url is the
|
|
|
|
|
address of the reverse proxy (e.g ``https://example.org/morty``).
|
|
|
|
|
|
|
|
|
|
For more information about *result proxy* have a look at *"searx via filtron
|
|
|
|
|
plus morty"* in the :ref:`nginx <nginx searx via filtron plus morty>` and
|
|
|
|
|
:ref:`apache <apache searx via filtron plus morty>` sections.
|
2019-12-30 18:31:17 +01:00
|
|
|
|
|
|
|
|
``url``
|
|
|
|
|
Is the address of the running morty service.
|
|
|
|
|
|
|
|
|
|
``key``
|
|
|
|
|
Is an optional argument, see `morty's README`_ for more information.
|
