VARASYS/ZDDC-website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ci: connect verify step to caddy via container name
All checks were successful
Deploy content to live site / deploy (push) Successful in 2s
Details

Browse source 
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.
This commit is contained in:
ZDDC 2026-05-02 11:35:09 -05:00
parent cacda0745d
commit e3ec3ae93c
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.forgejo/workflows/deploy-content.yml
View file

@ -30,5 +30,7 @@ jobs:
- name: Verify - name: Verify
run: | run: |
curl -ksI --resolve zddc.varasys.io:8443:127.0.0.1 \ # 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 https://zddc.varasys.io:8443/ | head -3