-
Notifications
You must be signed in to change notification settings - Fork 5
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
move to redis-namespace gem #6
Comments
No specific reason. Until you mentioned it, I had not heard of redis-namespace. As I am not familiar with the gem, would you explain why we should move to it? Will it require any API change for existing users of Lemondrop? Are there any pitfalls of which we should be aware? Perhaps we could allow Lemondrop users to select their Redis backend with a config option, if you feel it is important. |
The only reason I raised the request is to help users namespace their redis keys. A lot of popular libraries (sidekiq etc) have moved to |
I'm not opposed to this, but I still don't know enough about API changes in redis-namespace gem to feel comfortable moving the default behavior. My preference would be to do this as a configurable backend, with the default being the current |
There would be no API changes. |
Any specific reason for using
redis
gem?redis-namespace
gives namespaces, which would be a useful add-on.The text was updated successfully, but these errors were encountered: