Files
game-kit/template/deploy/deploy.sh
T

77 lines
3.7 KiB
Bash
Executable File

#!/usr/bin/env bash
# Build locally, push the static site and the game server to the droplet,
# and restart the server. Usage: deploy/deploy.sh <droplet-ip-or-host>
set -euo pipefail
HOST="${1:?usage: deploy.sh <droplet-ip-or-host>}"
# The family list is the kit's; a game deploys with the kit's latest copy when the kit is beside it.
KIT_FAMILY="$(dirname "$0")/../../game-kit/family.json"
[ -f "$KIT_FAMILY" ] && cp "$KIT_FAMILY" static/family.json
npm run check
npm run check:server
npm test
npm run build
# Every production ledger must replay identically with the engine about to ship.
deploy/verify-ledgers.sh "$HOST"
# Old hashed chunks stay a week: a page loaded before this deploy can still
# fetch the module it was built against instead of failing mid-game.
rsync -az --delete --filter='P _app/immutable/*' \
build/ "root@$HOST:/opt/__SLUG__/build/"
# The server runs from source with tsx and carries its own small manifest;
# it needs only its code and the engine. Ledgers live outside this tree.
rsync -az --delete --exclude='/server/node_modules' \
--include='/server/***' --include='/src/' --include='/src/lib/' --include='/src/lib/game/***' --include='/src/lib/net/' --include='/src/lib/net/view.ts' \
--include='/deploy/' --include='/deploy/__SLUG__.service' --include='/deploy/__SLUG__.cron' --include='/deploy/*.sh' --include='/deploy/traffic.py' \
--exclude='*' \
./ "root@$HOST:/opt/__SLUG__/app/"
ssh "root@$HOST" '
find /opt/__SLUG__/build/_app/immutable -type f -mtime +7 -delete
chown -R root:caddy /opt/__SLUG__/build
chmod -R g+rX /opt/__SLUG__/build
cd /opt/__SLUG__/app/server && npm install --no-audit --no-fund
chown -R __SLUG__:__SLUG__ /opt/__SLUG__/app
cp /opt/__SLUG__/app/deploy/__SLUG__.service /etc/systemd/system/__SLUG__.service
# The ops scripts run from /usr/local/bin and share traffic.py: install them
# on every deploy so the live copies are always the repo copies.
install -m 755 /opt/__SLUG__/app/deploy/__SLUG__-visitors.sh /usr/local/bin/__SLUG__-visitors.sh
install -m 755 /opt/__SLUG__/app/deploy/__SLUG__-pulse.sh /usr/local/bin/__SLUG__-pulse.sh
install -m 755 /opt/__SLUG__/app/deploy/__SLUG__-rollup.sh /usr/local/bin/__SLUG__-rollup.sh
install -m 755 /opt/__SLUG__/app/deploy/__SLUG__-backup.sh /usr/local/bin/__SLUG__-backup.sh
install -m 755 /opt/__SLUG__/app/deploy/__SLUG__-reseat.sh /usr/local/bin/__SLUG__-reseat.sh
# The key to the keeper door: made once, readable by root (the reseat script) and the game user (the server) alone.
if [ ! -s /etc/__SLUG__/keeper.key ]; then
install -d -m 750 -o root -g __SLUG__ /etc/__SLUG__
(umask 037; openssl rand -hex 32 > /etc/__SLUG__/keeper.key)
chown root:__SLUG__ /etc/__SLUG__/keeper.key
fi
install -m 644 -D /opt/__SLUG__/app/deploy/traffic.py /usr/local/lib/__SLUG__/traffic.py
# On a host the hall shares, its hall-nightly.sh runs the rollup and backup
# of every game and checks in with Sentry once for all; a game on a box of
# its own schedules its own.
if [ -f /etc/cron.d/gamehall ]; then rm -f /etc/cron.d/__SLUG__
else install -m 644 /opt/__SLUG__/app/deploy/__SLUG__.cron /etc/cron.d/__SLUG__; fi
mkdir -p /var/log/__SLUG__
systemctl daemon-reload
systemctl enable --now __SLUG__
systemctl restart __SLUG__
systemctl reload caddy
# "active" means only that the process started: wait for it to answer HTTP,
# so a server that dies loading its code fails the deploy instead of looping.
for i in $(seq 20); do
if curl -s -o /dev/null http://127.0.0.1:__PORT__/api/rooms/ZZZZ; then
systemctl --no-pager -l status __SLUG__ | head -3
exit 0
fi
sleep 1
done
echo "the game server is not answering:" >&2
journalctl -u __SLUG__ -n 25 --no-pager >&2
exit 1
'
echo "deployed."