Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to start version 2 of envy. (major version change since the important behavior will be changed)
The current behavior of envy is that it automatically loads
.env
file from the working directory and overwrites all pre-existing environment variables with the values from the.env
. However, this behavior is far from the general priority of configuration: the command-line argument is the first priority, followed by environment variables, otherwise using the configuration file as a default.Also, nowadays Cloud Computing and/or container technology became the standard runtime platform for applications and most of them provide environment variable-based runtime configuration with static virtual machine images or container images. So file-based configuration should be able to be overridden with environment variables.
After this, API clean-up will be followed before releasing v2.
fixes #36