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
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:
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: