b728696020
Removes the rsync --delete / manual-migration / no-rollback footguns from the deploy path. Validated: clean deploy passes the health gate; a forced health failure correctly rolls back from the .prev snapshot and recovers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
83 lines
3.3 KiB
Bash
Executable File
83 lines
3.3 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
set -uo pipefail
|
|
# NOTE: not `-e` — failures are handled explicitly so we can roll back.
|
|
|
|
# Deploy dev source to void2-app (CT 311) with a snapshot + health gate + auto
|
|
# rollback. Run from /project/src/void-v2.
|
|
#
|
|
# Override via env: TARGET=root@192.168.1.216 ./deploy/push.sh
|
|
# Target the LAN IP, NOT void2-app.hynesy.com (that's the CF tunnel, no SSH).
|
|
#
|
|
# What it does:
|
|
# 1. Snapshot the current remote code (excl node_modules/.env) -> <dir>.prev
|
|
# 2. rsync the new code in (--delete; preserves node_modules + .env)
|
|
# 3. npm install --omit=dev && npm run migrate (migrations are part of deploy)
|
|
# 4. systemctl restart void-server
|
|
# 5. Poll /health until it reports the EXPECTED version + db_ok (up to ~25s)
|
|
# 6. On any failure: restore the snapshot, reinstall, restart -> roll back
|
|
#
|
|
# Caveat: forward-only migrations are NOT auto-reverted on rollback. They're
|
|
# additive/backward-compatible by convention, so rolling the CODE back with the
|
|
# new schema present is safe. A destructive migration would need manual care.
|
|
|
|
TARGET=${TARGET:-root@192.168.1.216}
|
|
REMOTE_DIR=${REMOTE_DIR:-/opt/void-server}
|
|
PREV_DIR="${REMOTE_DIR}.prev"
|
|
HOST_IP="${TARGET#*@}"
|
|
HEALTH_URL=${HEALTH_URL:-http://${HOST_IP}:3000/health}
|
|
EXPECT_VERSION=$(node -p "require('./package.json').version")
|
|
|
|
RS_EXCLUDES=(--exclude node_modules --exclude .git --exclude tests --exclude coverage --exclude .env)
|
|
|
|
say() { printf '\n==> %s\n' "$*"; }
|
|
fail() { printf '\n!! %s\n' "$*" >&2; }
|
|
|
|
health_ok() {
|
|
# Returns 0 if /health reports EXPECT_VERSION and db_ok:true within the window.
|
|
local i body
|
|
for i in $(seq 1 25); do
|
|
sleep 1
|
|
body=$(curl -fsS -m4 "$HEALTH_URL" 2>/dev/null) || continue
|
|
if printf '%s' "$body" | grep -q "\"version\":\"${EXPECT_VERSION}\"" \
|
|
&& printf '%s' "$body" | grep -q '"db_ok":true'; then
|
|
return 0
|
|
fi
|
|
done
|
|
return 1
|
|
}
|
|
|
|
rollback() {
|
|
fail "Rolling back to the previous release"
|
|
ssh "$TARGET" "test -d '$PREV_DIR' && rsync -a --delete --exclude node_modules --exclude .env '$PREV_DIR/' '$REMOTE_DIR/' && cd '$REMOTE_DIR' && npm install --omit=dev >/dev/null 2>&1 && systemctl restart void-server" \
|
|
&& say "Rollback applied" || fail "Rollback command errored — check the host manually"
|
|
sleep 3
|
|
curl -fsS -m4 "$HEALTH_URL" >/dev/null 2>&1 && say "Service is responding after rollback." || fail "Service not responding after rollback — investigate on $TARGET"
|
|
}
|
|
|
|
say "Deploying ${EXPECT_VERSION} to ${TARGET}:${REMOTE_DIR}"
|
|
|
|
# 1. Snapshot current code for rollback (code only — fast; keeps node_modules/.env in place)
|
|
ssh "$TARGET" "mkdir -p '$PREV_DIR' && rsync -a --delete --exclude node_modules --exclude .env '$REMOTE_DIR/' '$PREV_DIR/'" \
|
|
|| { fail "Snapshot failed — aborting before touching the live release"; exit 1; }
|
|
|
|
# 2. Sync new code
|
|
rsync -az --delete "${RS_EXCLUDES[@]}" ./ "$TARGET:$REMOTE_DIR/" \
|
|
|| { fail "rsync failed"; rollback; exit 1; }
|
|
|
|
# 3 + 4. Install deps, run migrations, restart
|
|
if ! ssh "$TARGET" "cd '$REMOTE_DIR' && npm install --omit=dev && npm run migrate && systemctl restart void-server"; then
|
|
fail "install / migrate / restart failed"
|
|
rollback
|
|
exit 1
|
|
fi
|
|
|
|
# 5. Health gate
|
|
say "Health-checking for ${EXPECT_VERSION} ..."
|
|
if health_ok; then
|
|
say "Deployed ${EXPECT_VERSION} — healthy. ✓"
|
|
else
|
|
fail "Health check did not confirm ${EXPECT_VERSION} (db_ok) within the window"
|
|
rollback
|
|
exit 1
|
|
fi
|