4 ms·
Env vars are universally supported, globally available, and simple to manage. Files mean yet another deployment artifact that has to be stored somewhere, and no
by manigandham 7y ago
Env vars are universally supported, globally available, and simple to manage. Files mean yet another deployment artifact that has to be stored somewhere, and now tied to a location.
Sometimes that location is communicated through an env var, and that point why not just set all config that way?
- AlphaSite 7y agoIf you have something like k8s it becomes trivial to use files vs end vars.
- manigandham 7y agoHow so? You still have to edit the file, save it somewhere, then mount it as a volume and agree on a location.
- yencabulator 7y agoThe configuration file can be inline in the yaml, ConfigMaps take care of shuffling bytes around for you, and for a specific app it's config can always be at a fixed path.