The server has a lot of specific config vars, the configs can't all be within the code.
There needs to be central config method that all modules can pull from
The server has a lot of specific config vars, the configs can't all be within the code.
There needs to be central config method that all modules can pull from
The configs also can't be server specific, I think the database should be used for discord server specific configs, this way it can be updated in real-time. Examples of discord server specific variables are: WELCOME_CHANNEL_ID, IGNORED_CHANNEL_IDS, LINKCOP_RESTRICTED_CHANNEL_IDS
The database could also be used for other non-core configs. Core being things like MONGO_URL, SERVER_PORT, LOG_LOCATION
The configs also can't be server specific, I think the database should be used for discord server specific configs, this way it can be updated in real-time. Examples of discord server specific variables are: WELCOME_CHANNEL_ID, IGNORED_CHANNEL_IDS, LINKCOP_RESTRICTED_CHANNEL_IDS
The database could also be used for other non-core configs. Core being things like MONGO_URL, SERVER_PORT, LOG_LOCATION
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The server has a lot of specific config vars, the configs can't all be within the code.
There needs to be central config method that all modules can pull from
The configs also can't be server specific, I think the database should be used for discord server specific configs, this way it can be updated in real-time. Examples of discord server specific variables are: WELCOME_CHANNEL_ID, IGNORED_CHANNEL_IDS, LINKCOP_RESTRICTED_CHANNEL_IDS
The database could also be used for other non-core configs. Core being things like MONGO_URL, SERVER_PORT, LOG_LOCATION