Closed luni3359 closed 2 years ago
Partially fixed due to #36. On production, cogs shouldn't reload automatically, and the !reload
command should have a way to reload all cogs upon being used.
Using the bot's run.sh -u
command indirectly causes restartless updates to occur. Should the bash script be updated to make this the only way to update? Since, like previously mentioned, having extensions reload on production seems unsafe.
This is basically done. It doesn't seem feasible to make the bot 100% restartless, especially if core things have changed. As of now the bot updates via live reloads, but it will still need manual restarts until it manages to gracefully restart all cogs.
The amount of cogs spread among the project is astounding. Something should be done about that, but that's unrelated to this issue. To fully "automate" updates without restarts, we ought to use something like Docker.
Currently the user has to restart the whole bot to apply updates.