-
Notifications
You must be signed in to change notification settings - Fork 485
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
Handle URLs properly #93
Comments
I'd love to see your patch merged in. |
Thanks! The patch above is waiting for merge on PR #94. Hopefully someone can get to it soon. |
That would be cool to see this patch merged. |
Any chance of any movement on this? - It's becoming more inconvenient for me and I was hoping my PR would have been merged by now. Or is this blocked on issue #75? Please let me know if there's anything I can do to help get the PR merged. |
Fixes #93 by passing full URI to redis.createClient when specified
The [https://github.com/NodeRedis/node_redis](Node.js redis client) supports (and explicitly documents) fully-specified URLs, i.e.
[redis:]//[user][:password@][host][:port][/db-number][?db=db-number[&password=bar[&option=value]]]
.The socket.io-redis adaptor can only handle URLs of the form
hostname:port
.The text was updated successfully, but these errors were encountered: