-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Support redis socket url? #198
Comments
@ardecvz any thoughts? (you're the last one who touched Redis configuration code 🙂) |
Hey again, It looks like connecting to Unix Redis socket is already supported (since 1.4.5). You should be able to use |
@palkan We should consider reopening this issue because Unix socket support is currently broken. @sebyx07 please, use the last form if immediate support is required. |
@ardecvz I might be wrong but I believe the problem is not with slashes. No matter how many slashes I use in It seems a bit strange as according to rueidis source code, version 1.0.26 (used by the latest version @palkan any idea? |
Hey @lcmen, Can you please post the full output with the error? |
@palkan here it is:
|
@lcmen Hey 👋 I've also tested the integration - it's broken by default 😢 However, it's broken only for the backward-compatible Redis setup with pub/sub ( Therefore, you could use it right now - just don't forget to switch to it in the Rails app too ( More details here in the Go part and here in the Rails one. P.S.: you're likely interested in a new adapter for new app setups anyway to use a broker to keep persistent history. It seems that the old Redis lib Redigo also supports Unix sockets so I could patch the default broadcaster too if @palkan hasn't done it already and is OK with the plan? |
Let's do that! |
Thanks @ardecvz for very informative summary. One question: if I switch to |
Nope, these are different adapters. Pub/sub Redis is to be deprecated in v2.0; that's why it's still relying on a different Redis library. You can migrate to RedisX and use streams or even use HTTP adapter with Redis internal pub/sub (i.e., |
Thank you for clarification. We will switch to streams! |
Ruby supports pointing the path to the redis server,
is it possible for anycable to support it as well? the use case is: have an development enviroment with docker/docker-compose, where services like postgres, redis don't polute the localhost ports, and just listen to a socket file
The text was updated successfully, but these errors were encountered: