No description
  • C# 98.8%
  • Dockerfile 1.2%
Find a file
Dirk Kok 412c046c15
All checks were successful
Build and push Docker image / build-and-push-image (push) Successful in 16s
Build and push Docker image / trigger-update (push) Successful in 1s
update workflow for forgejo
2026-03-04 11:24:13 +01:00
.forgejo/workflows update workflow for forgejo 2026-03-04 11:24:13 +01:00
Botsome fixed 2025-11-10 20:22:40 +01:00
.gitignore working 2022-11-23 13:57:22 +01:00
Botsome.sln stop using docker-gen, and directly monitor docker 2022-09-13 17:35:00 +02:00
docker-compose.yml support substituting capture groups in responses 2025-01-22 12:33:21 +01:00
LICENSE Create LICENSE 2022-04-30 00:01:34 +02:00
README.md updated. still outdated tho 2022-09-16 15:50:47 +02:00

Botsome

Botsome monitors your docker containers and will steal use the bot tokens of your Discord bots to make them respond to certain events together. You can configure a trigger for a random bot to respond, or all of them at once.

As an unwanted side effect, if a bot container is running but isn't actually connected to Discord, the bot will still appear online because of Botsome's connection using its token.

Etymology

Botsome is the name of an emote in a series of "wholesome" derived emotes, in one of my servers.

Docker deployment

See docker-compose.yml for a working setup. Do not expose the app by publishing ports or running an ingress on the botsome-network, because it has no security measures in place whatsoever.

To make it use one of your bots, add the label me.foxite.botsome: true to its service (so you need to use a docker-compose file for your bots).

Botsome will read the environment variables of your bot. By default, it will use the contents of the BOT_TOKEN variable, but if you have your bot token in another viarable, specify its name in the me.foxite.botsome.envvar label.