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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more config options via ENV & Docker #760
Conversation
* correct the yaml synctax for the docker file * create an extra env file for the optional config stuff * modify the default config to respect the set env vars Signed-off-by: Christian Heusel <christian@heusel.eu>
Signed-off-by: Christian Heusel <christian@heusel.eu>
Signed-off-by: Christian Heusel <christian@heusel.eu>
Hi, thank you for the PR, looks good so far. I'm not sure about how useful the |
Yeah I also noticed that ... I will probably just move the env vars back into the I mean that is probably a design decision, but we could also remove some of the currently existing env options and remove this line from the Line 29 in dbf3737
I would like more env vars, thats why I wrote the PR this way :D |
Imho the only config in the compose file should be that one which needs to be changed to run there (so only mysql).
Baking config files into the container never was and never will be a good idea and should be avoided so the line should remain (and config files linked to containers on start). Creating a config file should only be required if some 'less used / technicaly problematic (shirts and other arrays)' configs have to be changed).
Thats definitely a good way, i agree -> more env vars are better! The plan is that at some time in the future most of them can be changed using the webinterface and the other more or less dynamically replaced by env vars but thats another issue ^^ |
I should had used *requests changes ;) |
Since I set up a version of the engelsystem via docker (:whale:) just now, I noticed that some of the config vars support being set via env and some dont.
I expanded the amount of variables that can be set and moved them into an extra env file.
I am very happy to discuss if people think a different approach would be more suitable! 馃槉