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
Today I've ran into an issue where generated images accidentally got deleted from disk, but cache (memcached) still kept info that generated images were created, so generateimages management command didn't generate new images. I know I can clear cache in that case, but didn't feel like messing with memcached since we are using it to store some other data. I ended up overriding generateimages command and adding image_file.generate(force=True).
I think that adding --force flag to generateimages might be useful for such scenarios. It looks like a simple change where generateimages --force would call image_file.generate(force=True), otherwise it would call image_file.generate().
If you agree I'll submit a pull request.
The text was updated successfully, but these errors were encountered:
Today I've ran into an issue where generated images accidentally got deleted from disk, but cache (memcached) still kept info that generated images were created, so generateimages management command didn't generate new images. I know I can clear cache in that case, but didn't feel like messing with memcached since we are using it to store some other data. I ended up overriding generateimages command and adding image_file.generate(force=True).
I think that adding --force flag to generateimages might be useful for such scenarios. It looks like a simple change where generateimages --force would call image_file.generate(force=True), otherwise it would call image_file.generate().
If you agree I'll submit a pull request.
The text was updated successfully, but these errors were encountered: