-
Notifications
You must be signed in to change notification settings - Fork 574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the strategy to deploy bot without downtime and without duplicated responses? #2478
Comments
This can get complicated depending on what your bot currently is doing, if your bot is running games it may need to pack currently running stuff into some kind of data to load later (probably a file). You then need to have the bot automatically pull in the version you want, lets say you're using Github. One way is having a command like
If the new bot fails, pull the old version back and compile and run, or if you went with the incremental approch just make old bot accept commands again. In case of complete failure of the move system, or invalid states and such, you could keep a way to communicate to your server through some other means, maybe a small extra bot that just listens in on the
I have never had issues with load but I can imagine one way that would work is if you had each bot instance only listening in on a specific amount of servers, with some kind of center server that manages which servers each bot-instance takes care of. |
Looks like this issue has been resolved with the response provided by @Brian-ED. If there's nothing more to add, perhaps this issue could be closed? |
Adding on to Brian's reply, another strategy is to use a gateway proxy such as Sandwich to proxy gateway responses from Discord to your bot |
I am new to bot development and I can't find solutions online to answer some of my questions. Also ChatGPT can't help with the design.
The text was updated successfully, but these errors were encountered: