Fix template env variable naming #6
Open
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
When I tried to use this template env file to create my own environment variables, I encountered the issue of non-matching variable naming between the env file and the settings.py, realized that here `STRIPE_PUBLISH_KEY` was used instead of `STRIPE_PUBLIC_KEY`. This commit changes this and fixes the faulty naming to the correct one.
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.
When I tried to use this template env file to create my own environment variables, I encountered the issue of non-matching variable naming between the env file and the settings.py, realized that here
STRIPE_PUBLISH_KEYwas used instead ofSTRIPE_PUBLIC_KEY. This commit changes this and fixes the faulty naming to the correct one.