ZDDC-website/.forgejo/workflows/deploy-content.yml
ZDDC e3ec3ae93c
All checks were successful
Deploy content to live site / deploy (push) Successful in 2s
ci: connect verify step to caddy via container name
Runner now runs in a quadlet container on caddy-net, so 127.0.0.1
is the runner's own loopback. Reach the Caddy container by name
('caddy') with --connect-to keeping SNI/Host as the public hostname
so the right vhost matches.
2026-05-02 11:35:09 -05:00

36 lines
1.1 KiB
YAML

name: Deploy content to live site
# Hand-edited site content lives in this repo. Every push to main
# rsyncs it into /srv/zddc/ on the deploy host (Caddy bind-mount).
# /releases/ is owned by the ZDDC source repo's pipeline and is
# excluded from this rsync; it's untouched here.
on:
push:
branches: [main]
workflow_dispatch:
jobs:
deploy:
runs-on: host
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Rsync content → /srv/zddc/
run: |
set -eu
rsync -av --delete-after \
--exclude='/releases/' \
--exclude='/.git*' \
--exclude='/.forgejo*' \
--exclude='/README.md' \
--exclude='/LICENSE' \
"$GITHUB_WORKSPACE/" /srv/zddc/
- name: Verify
run: |
# Runner is in a container on caddy-net; reach Caddy by container
# name. See deploy-release.yml in ZDDC for the same pattern.
curl -ksI --connect-to "zddc.varasys.io:8443:caddy:8443" \
https://zddc.varasys.io:8443/ | head -3