-
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
Support for Heroku style REDIS_URL env variables #353
Conversation
75da211
to
29290d9
Compare
So, fixed the tests and the code to comply with the projects extreme BC support :) |
Just a friendly ping :) |
Merged this great PR, thanks for your work @iKlaus! |
@snc Did you forget to tag this merge? |
@nicholasruunu No, I silently hope for some more feedback from successful uses ;-) |
@snc We're currently using this in two apps now, although both are still on stage. Both using redis for sessions and nothing else. |
This does not support phpredis
There is half of getters missing on RedisEnvDsn compared to RedisDsn... |
#378 includes related changes, it would be nice if some of you can test their setups. |
Sorry, but I am not using this anymore as it was causing problems back in the days... |
Being affected by the issue described in #302 I looked into what needs to be done to support Heroku's REDIS_URL environment variables. In short, they provide the credentials to a booked Redis addon via an environment variable which might change anytime at their discretion:
Therefor I just wanted to be able to make use of the
env()
dynamic parameter notation as inI came up with a rather simple approach which basically boils down to: