Add override for dev env variables with "dotenv" file #495
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
somaritane
requested review from
donovanmuller,
k0da,
kuritka and
ytsarev
as code owners
ytsarev
reviewed
May 20, 2021
Add possibility for persistent override of local dev environment variables with ".env" file. Signed-off-by: Timofey Ilinykh <[email protected]>
somaritane
force-pushed
the
dotenv-make-override
branch
from
55a33c3 to
1419098
Compare
kuritka
approved these changes
May 20, 2021
ytsarev
approved these changes
May 20, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds the possibility for persistent override of local dev environment variables with ".env" file.
A contributor can now store the environment variables with respective values in the
.envfile at the local repository root:cat .env # .env: LOG_LEVEL=info LOG_FORMAT=jsonOverrides done this way can persist between terminal sessions and can be used as a single point of configuration for development in terminal and IDE of choice. This removes the need to set environment variables separately for terminal and IDE, the experience remains consistent.
Signed-off-by: Timofey Ilinykh [email protected]