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

The host's Caddyfile gathers each game's site from /etc/caddy/sites/;
Wiz-War's is rendered from deploy/Caddyfile.tmpl and logs to
wizwar-access.log, which the rollup and the pulse read. The server's memory
cap drops from 700M to 350M (it runs in about 125M), so a runaway cannot
starve other games sharing the box. Applied on the live droplet with its
logs renamed in place.

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

deploy/README.md

@@ -35,8 +35,9 @@ longer replays becomes unreachable after restart, so this is not optional.
 
 1. `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`
-2. `scp deploy/setup-droplet.sh root@<ip>:/root/ && ssh root@<ip> \
-    "bash /root/setup-droplet.sh wizwar.<ip>.sslip.io"`
+2. `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)
 3. `deploy/deploy.sh <ip>`
 
 ## Operations