-
-
Notifications
You must be signed in to change notification settings - Fork 294
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
FloodUI not persisting config.json #807
Comments
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
@tomato4 It should save the Thanks |
I will look at it no later than at the end of the week and I will let you know, if it is fixed. |
Partially the problem is solved. If I set the variables in config and start container, the config is reflected in the settings (meaning if I set common_path, the common path is set in the settings). However if I change the settings in the app, the settings is NOT saved into the config file ( |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Every time the transmission is updated, the app looses it's configuration (eg. Common Paths). I tried to extract config.json (in /themes/flood-for-transmission) and bind it as external volume, but the mod just rewrites that. I tried to bind it as only RO, but the app just ignores the config (and in log is
cp: cannot create regular file '/themes/flood-for-transmission/config.json': Read-only file system
) and common paths in settings are empty.I didn't even find the configuration, where the app copies the config from default to try fix it.
This bug is very annoying, cause I either don't ever update the app or I have to assign common paths again and again.
The text was updated successfully, but these errors were encountered: