Skip to content
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

I'd like to be able to configure redis with multiple env variables #200

Closed
dramamask opened this issue Jun 2, 2023 · 0 comments · Fixed by #202
Closed

I'd like to be able to configure redis with multiple env variables #200

dramamask opened this issue Jun 2, 2023 · 0 comments · Fixed by #202
Assignees
Labels
enhancement New feature or request

Comments

@dramamask
Copy link

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:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants