-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
Why does DJANGO_REDIS_CONNECTION_FACTORY
need to be a global django setting ?
#619
Comments
Hello @vedantpuri, I see your issue, I think it's a valid point so we should have a pool per It should be quite simple, just pass If you do it yourself I would be glad to review and release a new version pretty quickly. Otherwise I can't promise I can do it reasonably fast as I don't have much time to dedicate to open source lately |
Sure! Here is a proposal: |
@WisdomPill hi, can you look at #680 please? |
@WisdomPill can we get a release with this feature? |
I released it yesterday, thanks @RealFatCat for the PR! 😄 |
Context
We use django-redis for our project and I am in a situation where I need to make only one of my caches sentineled.
Ideally the others should also be converted but due to time constraints and other reasoning based on usage we want to convert only one for now.
Question
When trying to change this I noticed that this setting is global, which means that all my caches need to be sentineled for this to work. I am not exactly sure why this is global and/or if this could be moved into OPTIONS per cache to provide more flexibility.
The text was updated successfully, but these errors were encountered: