Difficulty configuring Async::Job with Redis in production (works locally) #432
Replies: 1 comment
-
This is better asked on async-job's repo. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello 👋
First off, thanks for this amazing gem and for the eye-opening work on Async::Job!
I’m currently running in a Puma environment. I’m not quite ready to make the full Falcon jump yet, so I’ve been trying the “mixed” approach with Puma + Async::Job.
Everything works great locally 🎉, but I’m running into trouble getting it to work in production. I believe the issue comes down to configuring Async::Job::Processor::Redis with the correct Redis instance.
I already have a REDIS_URL environment variable set, and my initializer looks like this:
In production, I get this error:
Errno::EADDRNOTAVAIL: Cannot assign requested address - connect(2) for [::1]:6379
It feels like the Redis client is not picking up my REDIS_URL and is defaulting to localhost.
I searched through the various Async gems for guidance, but couldn’t find anything on how to pass connection details (e.g. REDIS_URL).
I’d love some pointers on how to properly configure this. Once I get it working, I’d be more than happy to open a PR to improve the Async documentation around Redis setup.
Thanks again for all the work you’re doing! 🙏
Beta Was this translation helpful? Give feedback.
All reactions