You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2024. It is now read-only.
I use an instance of Watchtower to automatically update all of my containers. When you pushed the most recent release, Watchtower updated my requestrr container and it refreshed everything. When I went to the web UI I got the create new user screen and none of the API keys or other settings were saved either, causing the bot to go offline.
Would it be possible to make all of the settings/connections/users persist between container updates? Thanks!
The text was updated successfully, but these errors were encountered:
nrgbistro
changed the title
[Bug] Settings not persistent when updated
[Feature Request] Settings not persistent when updated
Mar 31, 2020
Hey there, when using docker, you have to manually map the config folder of Requestrr (/root/config) to a folder outside of the container, otherwise when the containers update you will lose all your settings as they were stored inside the container.
You have to add the -v parameter when creating the container, like this:
-v /user/home/darkalfx/requestrr:/root/config
If you’ve done it and go into that folder, you should see two files: settings.json and notifications.json
I use an instance of Watchtower to automatically update all of my containers. When you pushed the most recent release, Watchtower updated my requestrr container and it refreshed everything. When I went to the web UI I got the create new user screen and none of the API keys or other settings were saved either, causing the bot to go offline.
Would it be possible to make all of the settings/connections/users persist between container updates? Thanks!
The text was updated successfully, but these errors were encountered: