[doc] improve admin-docs about result proxy (morty) configuration

[1] https://github.com/searx/searx/pull/1872#issuecomment-768107138

Suggested-by @dalf [1]
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>

1 files changed, 11 insertions, 4 deletions

diff --git a/docs/admin/morty.rst b/docs/admin/morty.rst
index 2858fde3c..5468c9c13 100644
--- a/docs/admin/morty.rst
+++ b/docs/admin/morty.rst
@@ -16,15 +16,22 @@ 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:
+``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 : your_morty_proxy_key
+        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.