Store secrets in separate .env file#718
Closed
0x326 wants to merge 4 commits into
Closed
Conversation
Member
|
I like the idea! |
0x326
force-pushed
the
store-secrets-in-separate-env-file
branch
from
3589c42 to
a4c8ff0
Compare
Author
|
@saghul Ok, it should be ready now |
This allows a downstream-user to keep .env under some version control without worrying about password leakage.
0x326
force-pushed
the
store-secrets-in-separate-env-file
branch
from
a4c8ff0 to
994eee8
Compare
|
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 allows a downstream-user to keep
.envunder some version control without worrying about password leakage.