BlokeBotHelp & guides

Technical operations

Run a BlokeBot server

Install the service, connect one Twitch application, provide trusted HTTPS and keep its private state backed up.

The BlokeBot admin page, showing you which controls are available to server owners. The BlokeBot admin page, showing you which controls are available to server owners.
The admin page allows you to configure the server to suit your needs, including allow lists for channels and manual channel setup.

1. Install and run

Choose Nix, Docker or a source checkout, give BlokeBot a persistent data directory, and start the dashboard on a private address while you finish setup.

2. Create the Twitch application

Create one Website Integration application in the Twitch Developer Console. Register both public HTTPS callbacks, then provide its Client ID and Client Secret to BlokeBot without checking the secret into source.

https://bot.example.com/auth/twitch/callback
https://bot.example.com/oauth/callback

3. Add HTTPS

Give the public dashboard a trusted HTTPS address. A typical deployment keeps BlokeBot on loopback behind Caddy, nginx or another reverse proxy that forwards the original scheme and host.

4. Keep state private and backed up

BlokeBot keeps its SQLite database, OAuth token cache and automatically managed Data Protection keys in private persistent application state. Restrict that state to the service account and back it up from a stopped service or one consistent snapshot.

5. Custom-bot credentials

Custom-bot encryption needs no operator configuration. ASP.NET Core manages Data Protection keys automatically in private persistent application state; Windows protects those keys with DPAPI LocalMachine.

A copied SQLite database or SQL backup does not expose reusable custom-bot tokens. Theft or compromise of the full state directory or the running host is outside that boundary.

When an upgrade finds old plaintext custom-bot credentials, it deletes them, disables that custom bot and alerts the channel owner to reconnect it.