-
Notifications
You must be signed in to change notification settings - Fork 325
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
Fix support for Heroku style REDIS_URL env variables #413
Conversation
3fc44dc
to
f3f1bc4
Compare
Can you rebase on current master? It should fix the tests. |
Co-authored-by: Klaus Großmann <kgm@petsdeli.de> Co-authored-by: Benoit Galati <benoit.galati@gmail.com>
@curry684 Done and also make some changes, thanks ;-) It looks good overall but I am not sure if it's breaking something else or not. |
I think tests should catch that, and it's going into master not right into stable. |
Thanks. What should I do to fix 2.1? |
Good job @B-Galati ! 🏅 👌 |
Thanks @B-Galati 😃 Merged it into master, not bothering with 2.1 anymore as it's pretty invasive and I'm trying to keep that one stable after recent issues, also the behavior has been broken for months already without many complaints. |
Hmm my bad, I thought it was broken before 2.1.0 already. I'll see if I can merge it back into 2.1. |
* Fix support for Heroku style REDIS_URL env variables Co-authored-by: Klaus Großmann <kgm@petsdeli.de> Co-authored-by: Benoit Galati <benoit.galati@gmail.com> * Add one simple test (cherry picked from commit 355251c)
See #356, we're reopening up an old issue here. |
Basically re-add what was done in #353
fixes #410
I also think that redis profile should not be resolved/interpolated in cache.