From bea8a2e1e1018361d99a4bf6e7617cfccebec2fe Mon Sep 17 00:00:00 2001 From: Eric Wagoner Date: Wed, 2 Sep 2026 09:13:01 -0400 Subject: [PATCH] deploy.sh installs the backup script it ships MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The droplet's cron ran /usr/local/bin/wizwar-backup.sh while the repo improved deploy/wizwar-backup.sh — two copies, no bridge, and the Sentry check-ins never reached the box, so the cron monitor starved and alarmed on 2026-09-02. Every deploy now installs the repo copy. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_015RCWSTnb1KYTPyL4GmhGnF --- deploy/deploy.sh | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/deploy/deploy.sh b/deploy/deploy.sh index c1646fe..9c3920c 100755 --- a/deploy/deploy.sh +++ b/deploy/deploy.sh @@ -11,6 +11,10 @@ ssh "root@$HOST" ' cd /opt/wizwar && npm install --no-audit --no-fund chown -R wizwar:wizwar /opt/wizwar cp /opt/wizwar/deploy/wizwar.service /etc/systemd/system/wizwar.service + # The backup script is cron-run from /usr/local/bin — install it every + # deploy, or the repo copy and the live copy drift apart (they did: + # the Sentry check-ins shipped in the repo and never reached the box). + install -m 755 /opt/wizwar/deploy/wizwar-backup.sh /usr/local/bin/wizwar-backup.sh systemctl daemon-reload systemctl enable --now wizwar systemctl restart wizwar