File: morty.rst

package info (click to toggle)
searx 1.1.0%2Bdfsg1-2
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 9,644 kB
  • sloc: python: 16,545; sh: 3,842; javascript: 2,104; xml: 1,071; makefile: 118
file content (40 lines) | stat: -rw-r--r-- 1,271 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

.. _searx morty:

=========================
How to setup result proxy
=========================

.. sidebar:: further reading

   - :ref:`morty.sh`

.. _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
``settings.yml``.  Add the following snippet to your ``settings.yml`` and
restart searx:

.. code:: yaml

    result_proxy:
        url : http://127.0.0.1:3000/
        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.

``url``
  Is the address of the running morty service.

``key``
  Is an optional argument, see `morty's README`_ for more information.