-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Adding auth to the redis store. #551
Conversation
Few comments on this, you really shouldn't throw an error when it fails, but just emit an error event for the store. |
-1 There are 2-3 important configuration parameters for running Redis in production. When I rewrote this, I chose this minimal configuration internally, which is already pretty noisy and repetitive, and set it up you coud easily pass in a fully configured RedisClient. Furthermore, the API for auth has changed quite a few times in node_redis and I'd rather not track this internally. The baseline parameters that we support internally have been stable for at least over a year, if not for the life of the project. These essential items are:
|
Oops, I was just chatting with @3rd-Eden and and I realized I referenced the internal property names in the post above. |
So, in case where auth is required - how would I do that here? |
@diversario Configure your instance of RedisClient externally and pass in the instance as indicated above.
|
Ah, that makes sense, thank you. |
np. |
`pingTimeout` now defaults to 5 seconds instead of 60 seconds.
Hi. I added auth to the redis store.
thx.