Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


There 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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: