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
28 lines
814 B
Cheetah
28 lines
814 B
Cheetah
# Wiz-War's site on a host shared with the other games of Kestrel's Hall:
|
|
# setup-droplet.sh fills __HOST__ and writes it to /etc/caddy/sites/wizwar.caddy.
|
|
__HOST__ {
|
|
header {
|
|
Strict-Transport-Security "max-age=31536000"
|
|
X-Content-Type-Options "nosniff"
|
|
X-Frame-Options "DENY"
|
|
Referrer-Policy "no-referrer"
|
|
}
|
|
|
|
# Kept to 30 rolls of 10MiB: the nightly rollup keeps the counts; the raw
|
|
# lines back it for a while. Each game on the host keeps its own log.
|
|
log {
|
|
output file /var/lib/caddy/wizwar-access.log {
|
|
roll_size 10MiB
|
|
roll_keep 30
|
|
}
|
|
}
|
|
|
|
# A deploy restarts the game for a few seconds; the proxy holds requests
|
|
# that land in that gap and keeps dialing, so a visitor waits instead of
|
|
# meeting a 502.
|
|
reverse_proxy localhost:8787 {
|
|
lb_try_duration 30s
|
|
lb_try_interval 250ms
|
|
}
|
|
}
|