[Koha-bugs] [Bug 26790] Refactor Koha configuration (koha-conf.xml)

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26790

--- Comment #13 from David Cook <dcook at prosentient.com.au> ---
(In reply to Tomás Cohen Arazi from comment #12)
> 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

I was thinking something like this as well. 

The other day I was setting up a Dockerized program on AWS ECS using Fargate,
and I used a combination of file-based configuration with environmental
variables passed by the orchestrator (ie AWS ECS) to override particular
relevant entries. 

Using Fargate was very cost effective (the bill is $0 since it's a very short
lived program) but it did make it more challenging in terms of providing
customized configuration files, since you don't have any control of the Docker
host. The de facto ECS approach there seemed to be to have an additional custom
container for pulling in configuration files from external sources and then
mounting them into to shared volume with the application container.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.