From 28b25185c51d320c8124292a6194e4c34fa9c3e8 Mon Sep 17 00:00:00 2001 From: Markus Heiser Date: Sun, 25 Apr 2021 12:03:54 +0200 Subject: [brand] searxng -- fix links to issue tracker & WEB-GUI Signed-off-by: Markus Heiser --- docs/blog/private-engines.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/blog/private-engines.rst') diff --git a/docs/blog/private-engines.rst b/docs/blog/private-engines.rst index 027cc3dd3..37b1d4cc5 100644 --- a/docs/blog/private-engines.rst +++ b/docs/blog/private-engines.rst @@ -12,7 +12,7 @@ would rather share engines only with their trusted friends or colleagues. Private engines =============== -To solve this issue private engines were introduced in :pull:`1823`. +To solve this issue private engines were introduced in :pull-searx:`1823`. A new option was added to engines named `tokens`. It expects a list of strings. If the user making a request presents one of the tokens of an engine, they can access information about the engine @@ -29,7 +29,7 @@ Example configuration to restrict access to the Arch Linux Wiki engine: Unless a user has configured the right token, the engine is going -to be hidden from him/her. It is not going to be included in the +to be hidden from him/her. It is not going to be included in the list of engines on the Preferences page and in the output of `/config` REST API call. @@ -42,7 +42,7 @@ is not carved in stone. As providing access to such engines implies that the admin knows and trusts the user, we do not see necessary to come up with a strict process. Instead, we would like to add guidelines to the documentation of the feature. - + Next steps ========== -- cgit v1.2.3