Fix default searx authentication setup
This commit is contained in:
parent
8e4c842ea9
commit
d41763f0dc
2 changed files with 21 additions and 3 deletions
|
|
@ -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: <hashed basicauth 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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue