Configuration using env vars

[gnometsunami]

I have deployed Spacebars official containers on kubernetes (it works great!) but managing the config.json file is a little cumbersome. I have worked around it by writing a copy of config.json into each container on startup.

Does the application write to config.json? Will my workaround (making local copies of the config.json for each running instance) cause configuration drift?

Would it be possible to set configuration parameters using env vars?

[CyberL1]

Spacebar validates the config and writes only the missing properties to it iirc, so if there are properties set already at the first start it shouldn't overwrite them

[TheArcaneBrony]

CONFIG_READONLY=1 can be set to disable filling in the missing parts of config

[gnometsunami]

That helps a lot. Thank you!

After looking at the application code, it seems like configuration should really be done with sql, right?

If I can rephrase my feature (or documentation) request: Expose env vars for everything that is required for startup

After the app starts, I could write a sql script to do any kind of post launch setup that I need.

[TheArcaneBrony]

we support (and recommend) json config, if there's anything i want to do, it's reducing env var usage
just set CONFIG_PATH=/path/to/config.json and you should be good to go