The documentation runs on Vercel; the Gateway bot needs a continuously running process. Use a VM or a container host that supports persistent connections. Build on the target platform, from your bot project:
go mod tidygo build -o bot ../botExport the same environment variables used locally. Closing the terminal or suspending the machine can stop the bot. On Linux, a systemd unit can supervise it:
[Unit]Description=DiscordKit support botAfter=network-online.targetWants=network-online.target
[Service]User=discordbotWorkingDirectory=/opt/discordkit-botEnvironmentFile=/etc/discordkit-bot.envExecStart=/opt/discordkit-bot/botRestart=on-failureRestartSec=5NoNewPrivileges=true
[Install]WantedBy=multi-user.targetCreate the unprivileged discordbot user, copy the binary to the path above, and create the environment file with your token and guild ID. Keep that file readable only by root (chmod 600); systemd reads it before switching users. Then run:
sudo systemctl daemon-reloadsudo systemctl enable --now discordkit-botsudo journalctl -u discordkit-bot -fSend SIGTERM for graceful shutdown. Start with one instance. For global distribution, choose an explicit global sync scope and remove test-guild duplicates deliberately; changing scope does not delete the old commands.