RbotLite (A tiny Discord bot)

Each environment requires two separate env files. This is intentional: the PostgreSQL container should not receive DISCORD_BOT_TOKEN.

Create them from the templates:

cp .config/.env.example .config/dev/.env.dev
cp .config/.env.postgres.example .config/dev/.env.postgres.dev

cp .config/.env.example .config/prod/.env.prod
cp .config/.env.postgres.example .config/prod/.env

The corresponding values must match between the files:

pip install uv
uv pip install -e .

uv pip install -e ".[lint]"

just dev

just prod

After adding the bot to a new server, a server administrator must run:

/admin_voice setup

This command stores the administrator role, target voice channel, request channel, and cooldown in PostgreSQL. Users can then submit a request with:

/admin_voice request

Requests themselves are not stored in the database. They stop being active after the bot restarts or the message containing their buttons expires.