-
-
Notifications
You must be signed in to change notification settings - Fork 497
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
Obsolete THUMBNAIL_KVSTORE #691
Comments
Love it. Let's do it! |
claudep
added a commit
to claudep/sorl-thumbnail
that referenced
this issue
Mar 1, 2022
claudep
added a commit
to claudep/sorl-thumbnail
that referenced
this issue
Mar 1, 2022
claudep
added a commit
to claudep/sorl-thumbnail
that referenced
this issue
Aug 20, 2024
claudep
added a commit
to claudep/sorl-thumbnail
that referenced
this issue
Aug 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think that the configurable KVStore adds complexity to the project without real added value, all the more that now Django also includes a Redis cache backend in core. What about only keeping
THUMBNAIL_CACHE
to point to some Django-configured cache and tell users to do the cache configuration at the Django project level?Are there still use cases to implement/specify custom KVStores that are not possible as Django cache backends?
@camilonova, would love to get your input on this idea.
The text was updated successfully, but these errors were encountered: