-
-
Notifications
You must be signed in to change notification settings - Fork 0
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 track of title configuration changes #83
Comments
First part is understood and much needed but the second part either I did not understand or it's not possible. If you want the CMS to adjust itself to a file rename on the storage backend, this won't happen. |
The second point is about #82 scenario, so about the CMS. I made a specific point about that because if we only track configuration changes, then such changes on the storage backend won’t be logged/tracked. |
I understand the need but I believe given our resources, it seems a lot more practical/realistic/safer to just forbid ourselves from manipulating the storage backend directly instead of building/maintaining this. |
@rgaudin Agree, we still need a trace, a log entry when done from the CMS. |
Already agreed in the beginning of my first comment… 🤷♂️ |
See #76 for event logging |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
Similar to openzim/zimfarm#498. Wee nee
An other point is that if someone renames a ZIM file in the storage backend we should keep track of that as well... even if the configuration has not formally changed!
The text was updated successfully, but these errors were encountered: