Currently, we are using a config.ini file to store our configuration settings. However, I believe it would be beneficial for us to migrate to using environment variables with a .env file instead.
By adopting the use of .env files, we would benefit from the following:
Widely adopted, and already defined in .gitignore by convention.
.env files provide a standardized way of managing environment specific configurations, such as our bot tokens, and follow the same structure as docker environment variable; The 2 could be implemented alongside each other very easily.
Reduced codebase size: currently in our config.ini setup we are defining xdg environment paths, this would be unneeded if we used .env, and overall all the code we're currently using to setup config.ini can be reduced to a few lines.
PROPOSAL
Currently, we are using a
config.inifile to store our configuration settings. However, I believe it would be beneficial for us to migrate to using environment variables with a.envfile instead.By adopting the use of
.envfiles, we would benefit from the following:.gitignoreby convention..envfiles provide a standardized way of managing environment specific configurations, such as our bot tokens, and follow the same structure as docker environment variable; The 2 could be implemented alongside each other very easily.config.inisetup we are definingxdg environment paths, this would be unneeded if we used.env, and overall all the code we're currently using to setup config.ini can be reduced to a few lines.