https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26790 --- Comment #12 from Tomás Cohen Arazi <tomascohen@gmail.com> --- (In reply to Julian Maurice from comment #11)
Yet another alternative would be to replace the main configuration file by environment variables. This is the approach recommended by https://12factor.net/config and can make working with containers (docker/k8s/...) easier.
Of course not everything can be put inside env vars, so it would probably be needed to have env vars that point to files. For instance LDAP_CONFIG_FILE=/etc/koha/sites/SITE/conf.d/ldap_config.yml
Another advantage: no need to worry about the main config file format, or an include mechanism
My vote would be: - Use separate files with expected names (config.yaml, shibboleth.yaml, etc) - No includes - Have C4::Context->config rebuild the 'old structure we already have, and deal with a different new handling on a separate bug (Koha::Config singleton implementation?) - Have a way for C4::Context->config to override any configuration if an env variable exists. e.g. KOHA_DATABASE_NAME should override the relevant entry. My two cents as well -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.