Updated main.py to use .env variables instead of config.init variables. #610
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
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.
Issue: We should move towards using the .env since this is the industry standard and existed in this codebase before config.ini was added. We'd like to stop using the config.ini and switch to only using the .env file.
Feedback Request: None yet, draft PR
Testing: Delete current config.init file and replace it with an empty .env file. Ensure the site runs without crashing. Replace the empty .env with the new .env. Ensure that the site runs without crashing and all components displaying data using .env variables display specific data rather than default data correctly.
Tasks Done in this PR: