Files
Void-Homelab/deploy/push.sh
root 941df0d0d2 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>
2026-06-01 17:49:08 +10:00

26 lines
788 B
Bash
Executable File

#!/usr/bin/env bash
set -euo pipefail
# Push dev source to void2-app (CT 311) and restart the service.
# Run from /project/src/void-v2.
#
# Override TARGET / REMOTE_DIR via env if needed:
# 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@192.168.1.216}
REMOTE_DIR=${REMOTE_DIR:-/opt/void-server}
rsync -avz --delete \
--exclude node_modules \
--exclude .git \
--exclude tests \
--exclude coverage \
--exclude .env \
./ "$TARGET:$REMOTE_DIR/"
ssh "$TARGET" "cd $REMOTE_DIR && npm install --omit=dev && systemctl restart void-server"
echo "Deployed."