-
Notifications
You must be signed in to change notification settings - Fork 0
Operations
alsi-lawr edited this page Jul 21, 2026
·
4 revisions
This technical section is for the person who maintains the BlokeBot server. Everyday dashboard problems are covered in Help and troubleshooting.
BlokeBot keeps operational state local and surfaces runtime problems through readiness and alert views.
- State and secrets - state locations, backups, and the custom-bot database boundary.
- Twitch identity and OAuth - application callbacks and what each login stores.
- HTTPS and reverse proxy - public origin and forwarding requirements.
- NixOS service - module options, systemd behavior, firewall, and hardening.
- Runtime health and delivery - readiness, alerts, reconnects, and durable public-chat outcomes.
Application state locations are summarized below. Keep the whole location private and backed up; explicit database or token-cache configuration can move an individual file elsewhere.
| Context | Application state |
|---|---|
| Native Linux |
$XDG_STATE_HOME/blokebot, or ~/.local/state/blokebot
|
| Native macOS | ~/Library/Application Support/BlokeBot |
| Native Windows | %LOCALAPPDATA%\BlokeBot |
| Docker | /data |
| NixOS | /var/lib/blokebot |
ASP.NET Core Data Protection keys for custom-bot credentials are created and persisted automatically in this private state. Windows protects them with DPAPI LocalMachine. No key-related operator settings or maintenance tasks are required.