📋 Operational Runbooks
Use these commands as operator starting points. Keep secret values out of chat and docs.
Quick reference
| Runbook | When to use | Command / path |
|---|---|---|
| Frontend deploy | After frontend or game-host changes | bash /home/usr/funday/scripts/build-atomic.sh |
| Frontend health | After deploy/restart | curl -sf http://127.0.0.1:3000/health |
| Nakama module build | After nakama-modules/*.ts changes | cd /home/usr/funday/nakama-modules && npm run build |
| Nakama restart | After verified Nakama bundle change | sudo k3s kubectl rollout restart deployment/nakama -n funday-platform |
| Wiki rebuild | After wiki content/config changes | cd /home/usr/funday/ssot.funday.gg && npx quartz build |
| Wiki watcher | Confirm auto-builder service | sudo systemctl status quartz-wiki |
| nginx reload | After nginx config changes | sudo nginx -t && sudo systemctl reload nginx |
| Ompcord daemon | After Amy/Ompcord config/code changes | node /home/usr/pi-discord-amy/amyd.mjs or its service wrapper |
Frontend deploy
cd /home/usr/funday
bash scripts/build-atomic.sh
curl -sf http://127.0.0.1:3000/healthUse --no-restart when staging a build without swapping/restarting.
Nakama deploy
cd /home/usr/funday/nakama-modules
npm run build
sudo k3s kubectl rollout restart deployment/nakama -n funday-platform
sudo k3s kubectl rollout status deployment/nakama -n funday-platform
curl -sf https://funday.gg/v2/healthcheckEdit TypeScript sources, then rebuild. Do not hand-edit generated nakama-modules/index.js.
Wiki update
cd /home/usr/funday/ssot.funday.gg
npx quartz build
sudo systemctl status quartz-wikiwiki.nginx.conf serves the generated public/ directory at ssot.funday.gg.
Ompcord/Amy checks
cd /home/usr/pi-discord-amy
bun test
node status.mjsDiscord tokens and API keys stay in local environment/config only.