fix(deploy): point deploy targets at CT 311 new IP .216

Post-outage recovery: a rogue OpenWrt device seized 192.168.1.13 after the
power-cut reboot, ARP-poisoning the LAN so CT 311 was unreachable despite being
healthy. Renumbered CT 311 .13 -> .216 (out of the conflict-prone low range,
next to the DB at .215). Update push.sh + push-workers.sh defaults to
root@192.168.1.216; push.sh no longer defaults to the void2-app hostname (that
resolves to the Cloudflare tunnel and can't carry SSH).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
root
2026-06-01 17:49:08 +10:00
parent 6cba2e82da
commit 941df0d0d2
2 changed files with 6 additions and 3 deletions

View File

@@ -4,7 +4,7 @@ set -euo pipefail
# Push Python void-workers source to CT 311 and restart the service.
# Run from /project/src/void-v2.
TARGET=${TARGET:-root@192.168.1.13}
TARGET=${TARGET:-root@192.168.1.216}
REMOTE_DIR=${REMOTE_DIR:-/opt/void-workers}
rsync -avz --delete \

View File

@@ -5,9 +5,12 @@ set -euo pipefail
# Run from /project/src/void-v2.
#
# Override TARGET / REMOTE_DIR via env if needed:
# TARGET=root@192.168.1.16 ./deploy/push.sh
# TARGET=root@192.168.1.216 ./deploy/push.sh
# NOTE: target the LAN IP, not void2-app.hynesy.com (that resolves to the
# Cloudflare tunnel, which can't carry SSH). CT 311 moved .13 -> .216 on
# 2026-06-01 after a post-outage ARP/IP conflict on .13.
TARGET=${TARGET:-root@void2-app}
TARGET=${TARGET:-root@192.168.1.216}
REMOTE_DIR=${REMOTE_DIR:-/opt/void-server}
rsync -avz --delete \