added URL support to createClient#658
Conversation
|
I remind you guys with indignation! 😃 |
|
Yes please! 👍 |
|
+1 |
1 similar comment
|
+1 |
|
Is there any blocker to merge that PR? |
|
👍 |
|
Yeah, would love to have this merged! |
|
PING @mranney @brycebaril |
|
+1 |
|
👍 need this |
|
wow,just noticed this was posted a while back and it is still open. Any chance we can get some feedback on this so that we are not waiting 10 months on an open ticket? If the feature is not welcomed then we can post a gist of simple alternative. If it is welcomed then I am sure @kuwabarahiroshi can do a pull+rebase since his PR is now behind master. |
|
I don't see any problems. If the unix socket test is passing (and it is), this should be merged. I'll merge it if we don't get any negative feedback soon. |
|
Wow, so many +1's. I'm so sorry that I haven't been spending time on this project lately. Please @erinspice make it happen, and if other people want commit access, I'll add you. |
|
You got it, @mranney! |
…-to-createClient added URL support to createClient
|
you guys rock |
|
Tip your waiters and waitresses! I'm here all night! |
|
Thanks for merging! |
|
\o/ :sparkles: thank you :-) |
Hi,
I thought it would be useful if we could specify redis server with URL string, like below:
This overloaded interface would be useful especially for node apps hosted on heroku, on which redis add-ons is usually provided via ENV variable.