-
Notifications
You must be signed in to change notification settings - Fork 549
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
Add support for passwords #54
Comments
I am not sure if i want to go down this path of adding more and more features that should be configurable somehow because then it could mean that more and more features would want to be added as somehow easy configurable. And it kinda breaks and moves away from the basic idea of this dockerfile as it should be used for a quick bootstrapping of a cluster that you can spin up and use for demos/tests/development and the basic feel from me is that if you need passwords in the base setup, you are probably using it wrong and not for those kinds of intended purposes. Adding a password feels like a production thing. |
We use docker in part so that we can have dev/prod parity; we would like to be able to have our development redis setup be as similar as possible to our production redis setup (which is why we're using a cluster in dev at all rather than a single redis instance). Ideally that would include being able to set a password. |
This is not a blocker for us or anything; we can work around it by configuring our redis location with a URL that does or does not include a password. I get it if it's not a feature you want to support. |
I will give it some more thought before deciding, but currently i am leaning towards not to support anything config based or dynamic stuff other then the bare minimum essentials like the IP variable that is required to even get it going. The idea of this one is not to have it production grade and compatible with all different types of systems and solutions. This is intended for dev/test types of environment and not much more. I think there is many other containers out there that would be possible to run at production quality instead of this one. My current recommendation is that you fork this and modify the config file to your needs and run with that. Or you can make a sub image that overrides the config file. The only case i would be willing to accept is to have something super generic that will enable anyone to have the ability to set any key:value in the config file. I am not up to speed with all options that docker support and if there is some new way to inject stuff during startup or not. If you have any suggestion in this direction i will consider it. |
This is the discussion on the docker redis image, there are few workarounds. It will be nice if we could at least override the command as in the redis vanilla image. See here:
It should not be a too terrible change |
It would require patching the supervisord scripts to allow the injection of the extra stuff. But unless i have access to the content of the variable |
If can set the password, this is perfect.Waiting for update. |
Fyi @Grokzen -- I implemented the option for both providing authentication for default user as well as a custom user through environment variables set during docker container build. It is backward compatible. LMK if you're intereseted in a PR to review. |
Is there any update on that? @Grokzen you suggested
I could not find any example that would work with |
Good idea, I have issues with auth on production, so I want test auth on local, too |
for those who need authentication, I've fork this repository to support authentication. |
@phuongdm1987 |
@phuongdm1987 |
@tmdgusya Here is the setup in my docker-compose file.
|
It would be great to be able to use docker-redis-cluster and put a password in front of it. It's not clear to me from the existing documentation whether that's possible; I'm fairly certain it isn't.
The text was updated successfully, but these errors were encountered: