> You also now have a config file: how is it stored?
Hum... Your environment variables must be stored at some place too, so the server can be launched. You can store the files at the exact same place.
Hum... Your environment variables must be stored at some place too, so the server can be launched. You can store the files at the exact same place.
But now you have multiple config files (smart) or your entire config outside the repo (not smart). This isn’t always the wrong approach — SSH keys get loaded this way, for instance.
ENV variables naturally provide a way to layer content from different sources in a way that files don’t, so if you have a relatively simple config from multiple providers (eg, getting AWS session token from the host plus your environment config from the launch ENVs) it’s easier to use the K-V store nature of ENV variables versus multiple files.
Again, multiple config files isn’t always wrong — but using that to store single strings instead of ENV variables is a code smell, for sure.