eric/hnefatafl
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
main
hnefatafl/deploy
T
History
Eric WagonerandClaude Opus 5.5 a2bdf7a825 The keeper's door asks for a key only root and the game's user can read, so another service on the host cannot re-seat anyone; the deploy makes the key once and the reseat script sends it from a file descriptor; and a seat link is taken out of the address bar with the browser's own call, since the page reads it before the router starts 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MbtUPJ24P6vc6tE1x6RS3m
2026-10-13 18:28:28 -04:00
..
__pycache__
A credibility pass over the whole repo: the board's mechanics in board.ts, one copy of each helper and stylesheet rule, the kit's plumbing this game never used removed, and the ops scripts counting traffic through one parser
2026-09-23 20:02:45 -04:00
Caddyfile.tmpl
Pages show the hall-wide notice, when there is one, at the top
2026-09-29 13:03:36 -04:00
deploy.sh
The keeper's door asks for a key only root and the game's user can read, so another service on the host cannot re-seat anyone; the deploy makes the key once and the reseat script sends it from a file descriptor; and a seat link is taken out of the address bar with the browser's own call, since the page reads it before the router starts
2026-10-13 18:28:28 -04:00
hnefatafl-backup.sh
The nightly rollup and backup say by their exit status whether they managed, and the deploy leaves the cron file off a host the hall schedules
2026-10-12 10:07:06 -04:00
hnefatafl-pulse.sh
Hnefatafl moves to the shared hall host
2026-09-25 16:56:33 -04:00
hnefatafl-reseat.sh
The keeper's door asks for a key only root and the game's user can read, so another service on the host cannot re-seat anyone; the deploy makes the key once and the reseat script sends it from a file descriptor; and a seat link is taken out of the address bar with the browser's own call, since the page reads it before the router starts
2026-10-13 18:28:28 -04:00
hnefatafl-rollup.sh
The nightly rollup and backup say by their exit status whether they managed, and the deploy leaves the cron file off a host the hall schedules
2026-10-12 10:07:06 -04:00
hnefatafl-visitors.sh
Traffic counts what matters: rooms opened from the site, where links were shared, scanners and monitors as bots
2026-09-27 09:59:38 -04:00
hnefatafl.cron
Begin Hnefatafl from the game kit
2026-09-23 12:45:44 -04:00
hnefatafl.service
A credibility pass over the whole repo: the board's mechanics in board.ts, one copy of each helper and stylesheet rule, the kit's plumbing this game never used removed, and the ops scripts counting traffic through one parser
2026-09-23 20:02:45 -04:00
pull-reports.sh
Hnefatafl moves to the shared hall host
2026-09-25 16:56:33 -04:00
README.md
The keeper can bring back a seat a browser lost: a new token on the ledger, the old one refused, and a link that carries it in the fragment, minted by hnefatafl-reseat.sh through a /keeper door Caddy does not proxy and that turns away anything Caddy forwarded; the join page takes a linked seat only once the server accepts it and never over a seat this browser holds that still opens, a spectator at a game in play is told both ways back, the hall asks before forgetting a game in play, and the server's tests now run with the rest
2026-10-13 18:24:31 -04:00
replay-ledgers.ts
A credibility pass over the whole repo: the board's mechanics in board.ts, one copy of each helper and stylesheet rule, the kit's plumbing this game never used removed, and the ops scripts counting traffic through one parser
2026-09-23 20:02:45 -04:00
report-digest.ts
A credibility pass over the whole repo: the board's mechanics in board.ts, one copy of each helper and stylesheet rule, the kit's plumbing this game never used removed, and the ops scripts counting traffic through one parser
2026-09-23 20:02:45 -04:00
report-reply.sh
A credibility pass over the whole repo: the board's mechanics in board.ts, one copy of each helper and stylesheet rule, the kit's plumbing this game never used removed, and the ops scripts counting traffic through one parser
2026-09-23 20:02:45 -04:00
sentry-slack-alert.sh
A credibility pass over the whole repo: the board's mechanics in board.ts, one copy of each helper and stylesheet rule, the kit's plumbing this game never used removed, and the ops scripts counting traffic through one parser
2026-09-23 20:02:45 -04:00
setup-droplet.sh
A credibility pass over ee5690e..HEAD: traffic.py parses each request once and counts visits one way, the deploy notes and skills agree with the scripts, and a few edit leftovers in the hall are tidied
2026-10-11 10:17:01 -04:00
traffic.py
A credibility pass over ee5690e..HEAD: traffic.py parses each request once and counts visits one way, the deploy notes and skills agree with the scripts, and a few edit leftovers in the hall are tidied
2026-10-11 10:17:01 -04:00
verify-ledgers.sh
A credibility pass over the whole repo: the board's mechanics in board.ts, one copy of each helper and stylesheet rule, the kit's plumbing this game never used removed, and the ops scripts counting traffic through one parser
2026-09-23 20:02:45 -04:00

README.md

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 (the determinism gate reads the ledgers from SITE; the sslip name answers wherever the real name does not resolve to this host yet).
  • 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 <id> <status> "text" answers one.

Adding this game to the host

  1. scp deploy/setup-droplet.sh deploy/Caddyfile.tmpl root@<ip>:/root/ && ssh root@<ip> \ "bash /root/setup-droplet.sh 'tafl.kestrelsnest.social, tafl.<ip>.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 <ip>

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 <your-key-ids> \ --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-reseat.sh ROOM [SEAT]: who sits at a table; with a seat, a new token for a player locked out of it, as a link to send them.
  • 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 <ip> 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 <ip>

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@<ip> 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@<ip> systemctl restart hnefatafl
  • Rooms: /var/lib/hnefatafl/rooms/<CODE>.jsonl, one ledger per game; the nightly backup keeps them in the Space.
Reference in New Issue View Git Blame Copy Permalink