You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to configure redis with multiple env variables, instead of just the REDIS_URL variable. For example:
REDIS_SCHEME
REDIS_HOST
REDIS_PASSWORD
REDIS_PORT
Unleash-edge could use those to assemble the correct redis URL. I'd prefer that since I now have to write my own logic to assemble the redis URL, taking things like password and scheme into account. Other services and frameworks use these types of env variables (e.g. Laravel).
Especially REDIS_SCHEME would be very helpful. You would configure either tcp or tls. Logic inside unleash-edge would then automatically use either redis:// or rediss:// as the prefix for the Redis URL.
The REDIS_PASSWORD variable would be very helpful to because the password needs to be included as part of the REDIS_URL right now. (See #199 for info on how to use a redis password)
Background
Right now I have to write my own logic to assemble the proper redis URL. We use different environments that require different REDIS_URLs (with or without password, some are tcp, some are tls).
Solution suggestions
No response
The text was updated successfully, but these errors were encountered:
Describe the feature request
I'd like to be able to configure redis with multiple env variables, instead of just the
REDIS_URL
variable. For example:Unleash-edge could use those to assemble the correct redis URL. I'd prefer that since I now have to write my own logic to assemble the redis URL, taking things like password and scheme into account. Other services and frameworks use these types of env variables (e.g. Laravel).
Especially
REDIS_SCHEME
would be very helpful. You would configure eithertcp
ortls
. Logic inside unleash-edge would then automatically use eitherredis://
orrediss://
as the prefix for the Redis URL.The
REDIS_PASSWORD
variable would be very helpful to because the password needs to be included as part of theREDIS_URL
right now. (See #199 for info on how to use a redis password)Background
Right now I have to write my own logic to assemble the proper redis URL. We use different environments that require different REDIS_URLs (with or without password, some are tcp, some are tls).
Solution suggestions
No response
The text was updated successfully, but these errors were encountered: