-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
redis-namespace asks to use admistrative commands directly #578
Comments
I don't really have a solution to that problem @Wolfer. For now, I've followed the Sidekiq approach of recommending against namespaces. Possibly, I could provide some type of administrative connection for this that the user configure. Not sure why they decided to prevent administrative commands. They created a lot of friction with that decision. Doesn't seem fair that I as a gem owner should have to provide extra configuration for a user of my gem to be able to fetch the redis version from the server itself. I'll have to do some thinking on this topic. I'm hesitant to create custom stuff for redis namespace. |
You are aware it is considered bad practice with redis namespace right? I'm not judging, maybe you have a project where that is outside of your control at the moment. I thought it worth mentioning at least. |
Yes, i know, but specific of project forces them to be used =( |
I found than Sidekiq provide method redis_info which incapsulate getting redis info correctly. Please, review my PR #581 |
#578 Co-authored-by: Mikael Henriksson <[email protected]>
Released as v7.0.5 |
thank you =) |
Version v7.0.6 was just released with an updated dependency @Wolfer |
When Sidekiq configured use redis namespaces like this
Deprecated text appears at startup
The text was updated successfully, but these errors were encountered: