SileNce/discord_bot_mgmt
1
0
Fork 0
mirror of https://github.com/SileNce5k/discord_bot_mgmt.git synced 2025-06-28 13:09:59 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

More thoughts

Browse source
This commit is contained in:
SileNce5k 2025-06-15 11:36:31 +02:00
parent 564768d32c
commit cc81f90713
No known key found for this signature in database
GPG key ID: 68C0A3A380BC32E9
1 changed files with 16 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

15
README.md
View file

@ -19,6 +19,21 @@
Bots will have an internal api that they communicate with the backend server over. Bots will have an internal api that they communicate with the backend server over.
Using websockets for the follow log is probably best? Using websockets for the follow log is probably best?
Actually, the simplest way would be to just use http requests all the way.
At least in the browser client. Browser queries server for new logs every x seconds, then updates the view if something changed.
Each discord bot would then need to have a HTTP server running that would respond to GETs by the mgmt backend.
This would update independently from the browser. Logs could be stored in a database table?
Something like:
```sql
CREATE TABLE logs (
id INTEGER PRIMARY KEY AUTOINCREMENT,
bot_name TEXT,
bot_ip TEXT,
entry TEXT,
date TEXT
)
```
### Misc Thoughts ### Misc Thoughts