4 ms·
The idea is the values in .env files can be configured via environment variables, while checks.yaml is for things that can be hard coded. In this case it's a b
by selcuka 2y ago
The idea is the values in .env files can be configured via environment variables, while checks.yaml is for things that can be hard coded.
In this case it's a bit moot because the yaml file works like a database, but when you deploy this using, say, Docker or k8s, you can use a different method to configure environment variables and skip .env files.
- librasteve 2y agogood question and answer … on a tangent, it makes me wonder if YAMLscript could be used to preload .env values on startup
- remram 2y agoWhy can't I change the port of my database server via an environment variable? This would be required for e.g. Nomad support. If this is a goal, why is it a goal for only half the configuration?
- jpitz 2y agoSomething I do in my yaml configs is support ${ENV} template variables with the string Template's substitute method using *os.environ.