-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
alsi-lawr edited this page Jul 21, 2026
·
3 revisions
This technical section is for the person who runs the BlokeBot server. Channel owners and moderators can use the User guide instead.
BlokeBot can run from a platform release archive, the repository Dockerfile, a Nix flake, or source.
| Target | Best for | Architectures |
|---|---|---|
| Platform release archive | A self-contained native installation | Linux x64/ARM64, macOS ARM64, Windows x64/ARM64 |
| Docker | A Linux host already running containers | Determined by the selected .NET base image |
| Nix | Reproducible package installation or direct execution |
x86_64-linux, aarch64-linux, aarch64-darwin
|
| NixOS service | Declarative, supervised deployment |
x86_64-linux, aarch64-linux
|
| From source | Development and local evaluation | Any platform supported by the pinned .NET and Node toolchains |
Extract the archive into its own directory and keep its files together. The executable is under bin/, not at the archive root:
./bin/blokebot help
./bin/blokebot serve --host 127.0.0.1 --port 8080 --data-dir /srv/blokebotOn Windows PowerShell:
.\bin\blokebot.exe help
.\bin\blokebot.exe serve --host 127.0.0.1 --port 8080 --data-dir C:\ProgramData\BlokeBot-StatePackage-manager availability varies by release and platform; use the release notes for the version being installed.
Add the Twitch configuration, provide public HTTPS, and confirm the state and backup location. There is no custom-bot encryption setup step.