[x] I just did this now (Mon 12/18/2023 - 08:54): try to run !editcom while the database wasn't up and running. The bot crashed, but part of the reason why is that I never handled any database errors, and I have that as one of the next TODO items. I should just test this same scenario.
[ ] Make sure that we can start the bot without the database being online.
[ ] Make a "fake" .env file so that I can keep the existing bot running
[ ] Work out how this should actually function. Should it keep trying to connect? Should it have a command-line interface where you can do things like reconnect?
!editcom
while the database wasn't up and running. The bot crashed, but part of the reason why is that I never handled any database errors, and I have that as one of the next TODO items. I should just test this same scenario..env
file so that I can keep the existing bot running