Skip to content
This repository has been archived by the owner on Jan 6, 2024. It is now read-only.

[Feature Request] Settings not persistent when updated #12

Closed
nrgbistro opened this issue Mar 31, 2020 · 2 comments
Closed

[Feature Request] Settings not persistent when updated #12

nrgbistro opened this issue Mar 31, 2020 · 2 comments

Comments

@nrgbistro
Copy link

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!

@nrgbistro nrgbistro changed the title [Bug] Settings not persistent when updated [Feature Request] Settings not persistent when updated Mar 31, 2020
@darkalfx
Copy link
Owner

darkalfx commented 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

@nrgbistro
Copy link
Author

That fixed it. My bad, I assumed it stored config in /config and not /root/config.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants