feat: add support for python-dotenv to store secret key #204
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.
Closes #196.
Current workflow:
.env
file doesn't exists then we create itFLASK_SECRET_KEY
is already set and we didn't specify--flask-secret-key
then don't touch itFLASK_SECRET_KEY
isn't set and--flask-secret-key
isn't set, then useos.urandom
to create cryptographically secure keyFLASK_SECRET_KEY
is set, but we specified--flask-secret-key
then we overwrite itNew changes:
.gitignore
, which we never usepython-dotenv
dependency to poetry file and also refresh lock file