The README suggest writing the main password in config.py if deploying locally. If backing up to a public Github repo in terms of security this is bad idea as the main password will then be visible to anyone to see. An alternative approach could be using a .env file and store the main password there then add the .env to a Github blacklist. There is a good post here (https://hackersandslackers.com/configure-flask-applications/) on how to achieve this under the "Configuration from a .py File" section
The README suggest writing the main password in
config.pyif deploying locally. If backing up to a public Github repo in terms of security this is bad idea as the main password will then be visible to anyone to see. An alternative approach could be using a.envfile and store the main password there then add the.envto a Github blacklist. There is a good post here (https://hackersandslackers.com/configure-flask-applications/) on how to achieve this under the "Configuration from a .py File" section