-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keep losing my settings.yml #7
Comments
The settings.yml is only replace if it has been updated in the docker image, but I agree it is not convenient. You can disable this behavior. In
The real fix would be a separate file searx.override.yaml update.sh requires more testing. |
ok i commented the line in thanks and searx is great |
FYI |
Okay :( May I ask you if you have these files :
|
i have |
The PR searx/searx#1668 should have fixed the issue (there is a version in hub.docker.com: 0.15.0-144-91a59ff3 ) This old PR might be interesting later: searx/searx#1278 but it requires some update. |
awesome!!! so do we need searx-checker? thanks |
Every 24h, searx-checker checks if your engines are working as expected. For the master branch, the result is here: https://searx.space/ (might be different for you because your IP is different). The purpose is:
In the future, searx-checker will be embedded in the searx docker image. |
I think the issue resolved. Additional note: look at searx/settings.yml.new file from time to time to see the updates. |
if i go to http://myip/status is says
|
Do you have rewrite / {
regexp ^/status$
to /searx-checker/status.json
} in your Caddyfile ? See https://github.com/searx/searx-docker/blob/master/Caddyfile#L60 If not, you should |
the rewrite code block is, as is in caddyfile |
In this case try Wait 10 minutes, if there is still nothing at https://..../status can you check these points ?
|
sorry for delayed response... |
Hello,
searx-docker works awesome, but watchtower updates it, and each time it updates my settings.yml get over written.
when i restore my settings.yml and restarting/build the container still doesn't work.
also on command update.sh, i get this error
fatal: --[no-]autostash option is only valid with --rebase.
am sure am doing something dumb, but cant figure it yet.
thanks
The text was updated successfully, but these errors were encountered: