12 Commits

Author SHA1 Message Date
Akulij
daf1e09176 delete unnecessary println
All checks were successful
Build && Deploy / cargo build (push) Successful in 1m5s
2025-06-02 16:51:19 +05:00
Akulij
de68e41725 create notificator 2025-06-02 16:49:05 +05:00
Akulij
f08af9609e sdfalkajsdfj
Some checks failed
Build && Deploy / cargo build (push) Failing after 10m46s
2025-06-01 13:39:10 +05:00
Akulij
f8628a11f5 make BotRuntime for js runtime management
Some checks failed
Build && Deploy / cargo build (push) Has been cancelled
2025-06-01 12:06:38 +05:00
Akulij
8b871ec147 fix: unnecessary BotController clone for script handler generation
All checks were successful
Build && Deploy / cargo build (push) Successful in 1m1s
2025-06-01 11:42:50 +05:00
Akulij
af85c57c67 change order of drop for BotController
Some checks failed
Build && Deploy / cargo build (push) Has been cancelled
2025-06-01 11:38:04 +05:00
Akulij
6dfe9b839d fix logic: move bot insertion to db to /deploy command, instead of function in bot_manager 2025-05-31 10:45:34 +05:00
Akulij
f27fb670bd create BotManager 2025-05-31 10:43:05 +05:00
Akulij
67ad3c2acd plug provided handlers in start_bot 2025-05-28 11:11:25 +05:00
Akulij
6eb6f2f454 fix: start bot with it's db name 2025-05-27 15:34:50 +05:00
Akulij
2fdd8a346d fix: instead of actually starting bot on /deploy, just put info in DB
reason: it's not a responsibility of /deploy command to store bot info
AND starting bot thread, isntead it is responsible only for storing info
in DB, as every other command does, and then bot will lazily start by
bot manager
2025-05-27 15:12:14 +05:00
Akulij
ef5d74cf1c create bot_manager module to handle background bot start 2025-05-27 04:17:05 +05:00