2 ms·
Generally, you swap out the config file at build time if that's a requirement. Just as a few examples - you can set up a dev/demo/prod(whatever you call these w
by ohaideredevs 8y ago
Generally, you swap out the config file at build time if that's a requirement. Just as a few examples - you can set up a dev/demo/prod(whatever you call these where you work) config file in .NET Core, Docker/K8S, Angular, etc. As far as I know, this is considered best practice.
- echelon 8y agoThere are many different needs. - static config - environment specification - runtime feature flagging - semi-static control plane config - rollout weights Etc. All of these have different characteristics. Infrequently changed, a priori config that doesn't need to be changed in emergencies is suitable for baking in at compile time.