Files

T

Eric WagonerandClaude Opus 5.5 56ea593e07 A deploy ships the engine's own data: only the top-level ledger folder is left behind

The exclusion for local game data matched any folder named data, so the
cards and boards the server reads never shipped after the droplet's first
setup; the live copy of cards.json had drifted to August's (text of FAQ
rulings, and rows of a set this edition does not deal). All 198 production
ledgers replay clean with the current data.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jm2auWk6RP71CjaAb4FMoG

2026-09-29 12:48:04 -04:00

lib

Credibility pass: the session seams sanded from the clips-and-camera batch

2026-09-03 11:55:57 -04:00

scene-goldens

The board's furniture and the reel's fists, painted as cels

2026-09-15 12:42:02 -04:00

brain-trial.mjs

Credibility pass: one teleport step, one bell, one step type, and the comments that argued are gone

2026-09-22 09:56:49 -04:00

Caddyfile.tmpl

Wiz-War's host follows the hall's shared layout: its own Caddy site file, its own access log, a memory cap for a shared box

2026-09-29 12:37:06 -04:00

clips-prep.mjs

Credibility pass: the session seams sanded from the clips-and-camera batch

2026-09-03 11:55:57 -04:00

clips-publish.sh

Clips unfurl: share cards, faststart video, a share button

2026-09-02 11:26:27 -04:00

deploy.sh

A deploy ships the engine's own data: only the top-level ledger folder is left behind

2026-09-29 12:48:04 -04:00

feedback-reply.sh

The desk's replies no longer ring the bell: reports and players' answers do, the desk's own mail does not

2026-09-23 08:54:08 -04:00

film-clips.mjs

The recorder takes one poster per clip

2026-09-03 19:39:13 -04:00

pull-feedback.sh

Reports are threads, and every turn of one rings the desk's bell

2026-09-21 12:08:55 -04:00

README.md

Wiz-War's host follows the hall's shared layout: its own Caddy site file, its own access log, a memory cap for a shared box

2026-09-29 12:37:06 -04:00

replay-verify.mjs

Credibility pass: the splice marks sanded from the rev-11 batch

2026-08-30 13:58:02 -04:00

sentry-slack-alert.sh

Credibility pass: one teleport step, one bell, one step type, and the comments that argued are gone

2026-09-22 09:56:49 -04:00

setup-droplet.sh

Wiz-War's host follows the hall's shared layout: its own Caddy site file, its own access log, a memory cap for a shared box

2026-09-29 12:37:06 -04:00

verify-ledgers.sh

Credibility pass: the accretion sanded smooth

2026-08-21 10:58:08 -04:00

verify-scenes.mjs

Credibility pass: the session seams sanded from the clips-and-camera batch

2026-09-03 11:55:57 -04:00

verify-scenes.sh

The render harness: every screenplay's beats pinned as golden frames

2026-09-01 16:58:43 -04:00

wizwar-backup.sh

Sentry plumbing, inert until a DSN exists

2026-09-01 09:58:26 -04:00

wizwar-rollup.cron

Credibility pass: comments say what the code can't, and the seams are gone

2026-09-16 00:21:34 -04:00

wizwar-rollup.sh

Wiz-War's host follows the hall's shared layout: its own Caddy site file, its own access log, a memory cap for a shared box

2026-09-29 12:37:06 -04:00

wizwar-visitors.sh

Credibility pass: comments say what the code can't, and the seams are gone

2026-09-16 00:21:34 -04:00

wizwar.service

Wiz-War's host follows the hall's shared layout: its own Caddy site file, its own access log, a memory cap for a shared box

2026-09-29 12:37:06 -04:00

README.md

Deploying Wiz-War

The game runs on a single DigitalOcean droplet: one Node process serves the built client and the websocket on port 8787; Caddy in front terminates TLS with automatic certificates. Room files persist in /var/lib/wizwar/rooms and survive deploys and reboots.

Current production

Droplet: wizwar (nyc3, s-1vcpu-1gb, tag wizwar), IP 104.236.96.198
URLs: https://wizwar.kestrelsnest.social and https://wizwar.104.236.96.198.sslip.io (always works, zero DNS). Caddy serves both; NOTE: kestrelsnest.social's authoritative DNS is at HOVER (ns1/ns2.hover.com), not DigitalOcean — records must be added there. A matching record also sits in the DO zone in case nameservers ever move.

Everyday deploys

deploy/deploy.sh 104.236.96.198

Builds the client locally, rsyncs the repo (minus node_modules, data/, .git, research), installs dependencies on the droplet, and restarts the service. Games in progress survive: state lives in room files, and clients reconnect automatically.

Before any deploy that touches the engine, run the determinism gate:

deploy/verify-ledgers.sh 104.236.96.198

It fetches every production ledger and strictly replays it against the local engine; a single refused command fails the check. A room whose ledger no longer replays becomes unreachable after restart, so this is not optional.

New droplet from scratch

doctl compute droplet create wizwar --region nyc3 --size s-1vcpu-1gb \ --image ubuntu-24-04-x64 --ssh-keys <your-key-ids> --tag-name wizwar --wait
scp deploy/setup-droplet.sh deploy/Caddyfile.tmpl root@<ip>:/root/ && ssh root@<ip> \ "bash /root/setup-droplet.sh 'wizwar.<ip>.sslip.io'" (the host's Caddyfile gathers each game's site from /etc/caddy/sites/, so the host can be shared)
deploy/deploy.sh <ip>

Operations

Logs: ssh root@<ip> journalctl -u wizwar -f
Restart: ssh root@<ip> systemctl restart wizwar
Nightly backups: wizwar-backup.sh runs from root's crontab at 07:17 UTC, pushing /var/lib/wizwar to the kestrel-wizwar-backups Space (nyc3) via rclone. It is installed at /usr/local/bin/wizwar-backup.sh on the droplet; setup-droplet.sh does NOT install it — on a fresh droplet, copy the script, configure rclone (the script refuses to run while the config still holds its CHANGE_ME placeholder), and add the cron entry by hand.
One-off backup: scp -r root@<ip>:/var/lib/wizwar/rooms ./rooms-backup