The keeper can bring back a seat a browser lost: a reseat line on the ledger gives that wizard's seat a new token and the old one opens nothing after, wizwar-reseat.sh on the host asks for it through a keeper door that listens on the loopback alone and opens only to a key the deploy makes once, and the link it prints carries the seat in the fragment, which leaves the address bar at once and is kept only when no seat held in this browser still opens and the server takes it; a gallery watching a game in play is told both ways back, the front page asks before forgetting a game not yet finished, and the server's tests now run with the rest
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MbtUPJ24P6vc6tE1x6RS3m
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
1b9acfd7c4
commit
5ea0d4fdec
@@ -9,6 +9,9 @@ WorkingDirectory=/opt/wizwar/packages/server
|
||||
Environment=PORT=8787
|
||||
# Caddy terminates TLS; the plaintext port must not face the internet.
|
||||
Environment=HOST=127.0.0.1
|
||||
# The keeper's door (deploy/wizwar-reseat.sh) binds the loopback whatever HOST says.
|
||||
Environment=KEEPER_PORT=9787
|
||||
Environment=KEEPER_KEY_FILE=/etc/wizwar/keeper.key
|
||||
Environment=WIZWAR_DATA_DIR=/var/lib/wizwar/rooms
|
||||
Environment=WIZWAR_STATIC_DIR=/opt/wizwar/packages/web/dist
|
||||
Environment=WIZWAR_KEEPER_TZ=America/New_York
|
||||
|
||||
Reference in New Issue
Block a user