From d41763f0dc6983e50968c21ba9adb2e76a49e302 Mon Sep 17 00:00:00 2001 From: Marty Oehme Date: Sat, 23 Oct 2021 22:15:06 +0200 Subject: [PATCH] Fix default searx authentication setup --- roles/searx/README.md | 18 ++++++++++++++++++ roles/searx/defaults/main.yml | 6 +++--- 2 files changed, 21 insertions(+), 3 deletions(-) diff --git a/roles/searx/README.md b/roles/searx/README.md index 31233d2..0d42d4a 100644 --- a/roles/searx/README.md +++ b/roles/searx/README.md @@ -29,3 +29,21 @@ subdomain_alias: search If the deployed container should be served over a uri that is not the stack name. By default, it will be set to `search.yourdomain.com` - if this option is not set it will be served on `searx.yourdomain.com` instead. + +``` +searx_authentication: + - username: mysearxusername + password: +``` + +By default, the searx instance is not protected with a login, however you +can have caddy provide a basic auth login form by using this variable. + +You can either change the login to suit you by generating a combination +(or multiple, it will also work with an arbitrary amount of logins), +or remove the necessity to login altogether by not setting the +`searx_authentication` variable to anything. + +The password needs to be in a hashed format, which is easiest to accomplish +with the help of caddy itself --- simply doing `caddy hash-password` will +allow you to create a new hashed password. diff --git a/roles/searx/defaults/main.yml b/roles/searx/defaults/main.yml index de1cc15..b129040 100644 --- a/roles/searx/defaults/main.yml +++ b/roles/searx/defaults/main.yml @@ -9,6 +9,6 @@ searx_use_https: true # the subdomain link searx will be reachable under subdomain_alias: search -searx_authentication: - - username: mysearxusername - password: JDJhJDE0JFdjUnQ5WWllcU8wa01xS0JBS2dlMy5zMEhRTmxqTXdIZmdjcTN6ZGFwRjJlYUdoSHAwRUhL # mysearxpassword +# searx_authentication: +# - username: mysearxusername +# password: JDJhJDE0JFdjUnQ5WWllcU8wa01xS0JBS2dlMy5zMEhRTmxqTXdIZmdjcTN6ZGFwRjJlYUdoSHAwRUhL # mysearxpassword