# Deploying Hnefatafl Every game is a room on a small Node process that keeps it as an append-only ledger of moves in /var/lib/hnefatafl/rooms. Production is the shared Kestrel's Hall host: Caddy terminates TLS with automatic certificates, serves the static build from /opt/hnefatafl/build, and proxies /api and /ws to the game server on port 8789, which runs as the `hnefatafl` user under systemd from /opt/hnefatafl/app. ## The shared host The games of Kestrel's Hall share one droplet, `hall` (nyc3, s-1vcpu-1gb, $6 a month, tag `kestrels-hall`, IP 159.203.115.252). Each game keeps its own Caddy site file in /etc/caddy/sites/.caddy, its own port, service user, /opt/ and /var/lib/ trees, access log (/var/lib/caddy/-access.log), cron file and ops scripts; /etc/caddy/Caddyfile only says `import sites/*.caddy`. A game server is one small Node process capped at 300 MB by its unit file, and a room is a few kilobytes of ledger, so the host carries several. Each game needs a port of its own on the host: wizwar 8787, waving-hands 8788, hnefatafl 8789, dip 8790. ## Current production - Host: 159.203.115.252 - URLs: https://tafl.kestrelsnest.social (A record at Hover, where kestrelsnest.social's DNS lives) and https://tafl.159.203.115.252.sslip.io (always works, zero DNS). - Everyday deploy: `SITE=https://tafl.159.203.115.252.sslip.io deploy/deploy.sh 159.203.115.252` (this Mac's resolver caches the old *.kestrelsnest.social wildcard, so the gate reads the sslip name). - Moved here from its own droplet (209.97.148.244) on 2026-09-25. - Players' reports: `deploy/pull-reports.sh` mirrors /var/lib/hnefatafl/feedback.jsonl and the screenshots to ~/Desktop/hnefatafl-reports with a digest; `deploy/report-reply.sh 159.203.115.252 "text"` answers one. ## Adding this game to the host 1. `scp deploy/setup-droplet.sh deploy/Caddyfile.tmpl root@:/root/ && ssh root@ \ "bash /root/setup-droplet.sh 'tafl.kestrelsnest.social, tafl..sslip.io'"` It installs Caddy and Node if the host lacks them, writes this game's site file, and touches nothing of another game's. Point the A record at the host first, or leave the real name out until it is; running it again with the new line is how a name is added later. 2. `deploy/deploy.sh ` A fresh host, when one is needed: `doctl compute droplet create hall --region nyc3 \ --size s-1vcpu-1gb --image ubuntu-24-04-x64 --ssh-keys \ --tag-name kestrels-hall --wait`, then step 1. ## Operations scripts on the droplet `deploy.sh` installs these to /usr/local/bin, the `traffic.py` they share to /usr/local/lib/hnefatafl, and the cron file to /etc/cron.d/hnefatafl on every deploy, so the live copies are the repo copies: - `hnefatafl-visitors.sh [day]`: who is here now and who came that day. - `hnefatafl-pulse.sh`: the weekly health check (service, errors, rollup trend, backup, box). - `hnefatafl-rollup.sh [day]`: one JSON line per day of counts, run nightly at 00:12 UTC into /var/lib/hnefatafl/rollup.jsonl. - `hnefatafl-backup.sh`: nightly at 07:23 UTC, mirrors /var/lib/hnefatafl to the `kestrel-wizwar-backups` Space under `hnefatafl/` (a current copy and dated snapshots kept 90 days). It needs rclone with the Spaces credentials in /root/.config/rclone/rclone.conf, copied by hand from the wizwar droplet; until then it logs "skipped". Errors from the game server go to Sentry, project `hnefatafl` in the locallygrownnet organisation; the DSN is in the unit file. The nightly rollup and backup check in with Sentry Crons when /root/.hnefatafl-sentry-cron-rollup and /root/.hnefatafl-sentry-cron hold their check-in URLs (the ingest URL with the project's cron path and public key), so a missed night is noticed. To have every new issue, regression and reappearance posted to Slack the way wizwar's are, run `deploy/sentry-slack-alert.sh [#channel]` once from your own shell with `SENTRY_TOKEN` (an org auth token with alerts:write) and `SLACK_CHANNEL_ID` (the channel's Slack ID) set; the token never leaves the shell. Before every deploy, `deploy/verify-ledgers.sh ` fetches every production ledger and replays it with the local engine, comparing each room with what the server shows. A ledger the new engine refuses or replays differently stops the deploy: the server would rewrite that game on restart. ## Everyday deploys deploy/deploy.sh Runs the type-checks, the tests and the build locally, rsyncs `build/` to the droplet keeping the previous week's hashed assets, rsyncs the server and engine sources, installs dependencies, and restarts the game server. A room is replayed from its ledger when the server comes back, which takes a few seconds; Caddy holds requests that land in the gap. ## Operations - Logs: `ssh root@ journalctl -u hnefatafl -f` for the game server, `journalctl -u caddy -f` and /var/lib/caddy/access.log for the web side. - Restart: `ssh root@ systemctl restart hnefatafl` - Rooms: `/var/lib/hnefatafl/rooms/.jsonl`, one ledger per game; the nightly backup keeps them in the Space.