I usually work on Django with the standard "settings file" approach and manage the scenarios you have listed, such as secret passwords, database settings, SMTP settings, ssl settings, specific settings for deployment and staging, in short all with:
dotenv module and a .env local file ignored by version control.
local I have my environment variables ( in a only file) and can run without ssl, can use email console backend, can have debug mode on, and sqlite3 db;
Heroku is set with its environment variables...and postgres db;
Digital Ocean has its environment variables;
my friend has his environment variables too
However, your module is very interesting and useful, as it is really difficult to manage the settings when you are a beginner. well done
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I usually work on Django with the standard "settings file" approach and manage the scenarios you have listed, such as secret passwords, database settings, SMTP settings, ssl settings, specific settings for deployment and staging, in short all with:
dotenv module and a .env local file ignored by version control.
local I have my environment variables ( in a only file) and can run without ssl, can use email console backend, can have debug mode on, and sqlite3 db;
Heroku is set with its environment variables...and postgres db;
Digital Ocean has its environment variables;
my friend has his environment variables too
However, your module is very interesting and useful, as it is really difficult to manage the settings when you are a beginner. well done