chore: one-command static deploy
The homelab has no rsync, so the tree goes over as a tar stream, and the destination is wiped first - a stale content-hashed chunk left behind would be served forever, since /assets/* is cached as immutable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
96f273ce2b
commit
71071cff94
3 changed files with 45 additions and 1 deletions
25
tools/deploy.sh
Executable file
25
tools/deploy.sh
Executable file
|
|
@ -0,0 +1,25 @@
|
|||
#!/usr/bin/env sh
|
||||
# Build and publish to [removed].
|
||||
#
|
||||
# The homelab has no rsync, so the tree goes over as a tar stream. Caddy serves
|
||||
# /mnt/docker/appdata/caddy/sites/[removed] as /srv/[removed] (a
|
||||
# read-only bind mount declared in /mnt/docker/compose/caddy/docker-compose.yml),
|
||||
# so a deploy is a file copy - no container restart, no config reload.
|
||||
set -eu
|
||||
|
||||
HOST="${DEPLOY_HOST:-hl}"
|
||||
DEST="${DEPLOY_DEST:-/mnt/docker/appdata/caddy/sites/[removed]}"
|
||||
ROOT="$(cd "$(dirname "$0")/.." && pwd)"
|
||||
|
||||
cd "$ROOT"
|
||||
rm -rf dist
|
||||
# build:single runs the hosted build first, so this produces both targets.
|
||||
npm run build:single
|
||||
|
||||
# Replace rather than merge: a stale content-hashed chunk left behind would be
|
||||
# served forever, since /assets/* is cached as immutable.
|
||||
tar -C dist -cz . | ssh "$HOST" "rm -rf '$DEST'/* && tar -C '$DEST' -xz"
|
||||
|
||||
printf '\ndeployed. checking...\n'
|
||||
curl -fsS -o /dev/null -w '[removed] -> %{http_code}\n' [removed]
|
||||
curl -fsS -o /dev/null -w '[removed] -> %{http_code} (%{size_download} bytes)\n' [removed]
|
||||
Loading…
Add table
Add a link
Reference in a new issue