myenv 201902.7

For each annoatated member of ^{} declare the 1. name, 2. type and 3. an optional default variable. Members without a default must be set by an environment variable or configuration file, otherwise a ^{} will be raised.

Parsing

To use the above configuration class, simply instanciate it.

In case you're worried about the instantiation of ^{}, it will return a singleton instance, so the ^{} and configuration files are parsed only once.

Config Files

When parsing configs, the following paths are parsed if they exist. By default the configs are loaded from ^{}, but you can override the location of configuration files by setting the environment variable ^{}.

• ^{}
• ^{}

Any variables defined in these files will be set, unless it was already set in the environ or a previous config file.

This approach allows you to satisfy typical use cases in which a service is hosted:

1. Development Machine
2. Stage/Production Environment

You can put use case specifc configuration files in your project source tree, such as:

• ^{}
• ^{}
• ^{}

To parse the appropriate config file, all you have to do is set a single environment variable ^{}. If ^{} is not set, it will fall back to ^{}.

The ^{} config files are flat text files, with one KEY=value mapping per line. The only lines which are parsed, are lines which begin with an all upper case token, followed by an ^{} character:

For sensitive configuration parameters, such as passwords and authentication tokens, you may prefer to write config files outside of your source tree, or to provide them always and only via environment variables.