-
Notifications
You must be signed in to change notification settings - Fork 333
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
Database Connection - Use environment variables (optional setting) #4791
Comments
This is similar to #4784, except that it concerns the install process, while your proposed solution would be bypassing the install for MySQL config, am I right? |
Exactly, my solution would only bypass the MySQL part of the installation, since the values will be dynamic. Only an initial connection check would be needed. |
Here's my question then: do we need to choose between either implementation or can we have both at the same time? |
It should be possible to use both at the same time, I would build my approach on top of #4784 's approach, as an extra checkbox/parameter during installation which activates either the "normal" or the "getenv" mode. |
Then by all mean, submit a PR. |
Fixed by #4855 |
Documentation needed. |
I just added the label, hopefully someone (maybe you?) will pick up on it. |
@M-arcus could you write the docs for this? |
@tobiasd yes, will do |
Thank you for your work! |
I am currently creating a Dockerfile for a selfhosted server-solution (cloudron). During first testing, I have encountered the following problem:
Problem
The MySQL credentials change at every start of the docker container, meaning the container only works at the first run. But the MySQL credentials can be accessed per
getenv()
.Proposed solution:
Add a config setting 'Get MySQL-Connection from Environment Variables'
Set the default
false
, so it doesn't break anything for existing installations.If set to
true
, the credentials will be taken from the Environment Variables pergetenv()
.I would open a PR for it, if you agree to adding this feature
The text was updated successfully, but these errors were encountered: