From 56ea593e07c49e0b89c439fee7cae880b3ade3e3 Mon Sep 17 00:00:00 2001 From: Eric Wagoner Date: Tue, 29 Sep 2026 12:48:04 -0400 Subject: [PATCH] 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 Claude-Session: https://claude.ai/code/session_01Jm2auWk6RP71CjaAb4FMoG --- deploy/deploy.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy/deploy.sh b/deploy/deploy.sh index 3562aa1..8dcac64 100755 --- a/deploy/deploy.sh +++ b/deploy/deploy.sh @@ -8,10 +8,12 @@ KIT_FAMILY="$(dirname "$0")/../../game-kit/family.json" [ -f "$KIT_FAMILY" ] && cp "$KIT_FAMILY" packages/web/public/family.json npm run build --workspace=@wizwar/web +# /data/ is the local game ledgers, anchored so the engine's own data/ (the +# cards and boards the server reads) always ships. # Old hashed chunks stay a week: a page loaded before this deploy can still # fetch the module it was built against instead of failing mid-game. rsync -az --delete --filter='P packages/web/dist/assets/*' \ - --exclude node_modules --exclude data/ --exclude .git --exclude research \ + --exclude node_modules --exclude /data/ --exclude .git --exclude research \ ./ "root@$HOST:/opt/wizwar/" ssh "root@$HOST" ' cd /opt/wizwar && npm install --no-audit --no-fund