deploy.sh installs the backup script it ships

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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015RCWSTnb1KYTPyL4GmhGnF
This commit is contained in:
Eric Wagoner
2026-09-02 09:13:01 -04:00
co-authored by Claude Fable 5
parent 58d1d34cb0
commit bea8a2e1e1
+4
View File
@@ -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