-
Notifications
You must be signed in to change notification settings - Fork 0
Configuration
This technical section is for the person who runs the BlokeBot server. Most channel owners and moderators do not need these settings.
BlokeBot uses standard ASP.NET Core configuration. Base settings describe the full shape; environment variables and environment-specific files supply deployment values.
- Sources and runtime activation - precedence, CLI options, state-path overrides, environment-variable names, and runtime activation.
- Core settings - logging, administrators, cooldowns, and database location.
- Configure a Twitch developer application - create the application, register BlokeBot callbacks, and retrieve its client ID and secret.
- Twitch identity and OAuth - dashboard sign-in, channel connection, bot identities, scopes, and callbacks.
- Chat runtime - EventSub, IRC, message limits, connection settings, and queue alerts.
- Retry and delivery policies - reconnect, retry, lifetime, and retention controls.
Replace each : in a configuration path with __:
TwitchBot:Identity:ClientId
TwitchBot__Identity__ClientId
Keep client secrets out of Nix expressions, command history, images, and tracked settings. Custom-bot encryption has no operator settings; its keys are managed automatically in private persistent application state.
BlokeBotSite:LiveAppUrl controls the live-app call to action on the Site home page. A missing, blank, or whitespace-only value disables the entire call-to-action section. An absolute HTTP or HTTPS URL enables the section and becomes its link target. Any other value fails Site startup with a configuration error.
The footer on every Site page shows Site {version}. This is the BlokeBot.Site product version, independent of the running bot version.