christian/waters-boards
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

Note that the Chronicles-AB runner uses host networking
Deploy Waters Boards to AWS / deploy (push) Successful in 1m58s
Details

Browse Source 
Bridge-network containers on that NAS have no outbound NAT, so the first run
failed fetching actions/checkout. The runner and job containers now share the
host network.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
michael
2026-10-15 11:13:31 -04:00
co-authored by Claude Fable 5.1
parent ecfb26d40a
commit e50c3a0c1e
2 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+4
View File
@@ -8,6 +8,10 @@
# healthcheck. All of that is deploy/aws/deploy.sh, the same script you run from a laptop. # healthcheck. All of that is deploy/aws/deploy.sh, the same script you run from a laptop.
# The checklist app's "nas" runner on Chronicles-NA is not involved. # The checklist app's "nas" runner on Chronicles-NA is not involved.
# #
# That runner and its job containers use Docker host networking: containers on bridge
# networks on Chronicles-AB have no outbound NAT (no DNS, no internet), which made the first
# run fail while fetching actions/checkout.
#
# ONE-TIME SETUP before the first run (see README.md › Deploy to AWS): # ONE-TIME SETUP before the first run (see README.md › Deploy to AWS):
# 1. Make a deploy-only SSH key (e.g. ssh-keygen -t ed25519 -N '' -f deploy_key) and add the # 1. Make a deploy-only SSH key (e.g. ssh-keygen -t ed25519 -N '' -f deploy_key) and add the
# public half to /home/ubuntu/.ssh/authorized_keys on the box. # public half to /home/ubuntu/.ssh/authorized_keys on the box.
README.md
+3 -1
View File
@@ -130,7 +130,9 @@ to deploy to a host other than `boards-aws`.
so AWS can't pull from it. Instead a runner inside the network runs the same `deploy.sh` and so AWS can't pull from it. Instead a runner inside the network runs the same `deploy.sh` and
pushes to the box over SSH. That runner is a container on Chronicles-AB (the NAS that hosts pushes to the box over SSH. That runner is a container on Chronicles-AB (the NAS that hosts
Gitea), in `/volume2/docker/gitea-runner-boards`, registered for this repo only with the label Gitea), in `/volume2/docker/gitea-runner-boards`, registered for this repo only with the label
`aws-deploy`. The checklist app's `nas` runner on Chronicles-NA is separate and untouched. The workflow `aws-deploy`. The checklist app's `nas` runner on Chronicles-NA is separate and untouched. The
runner and its job containers use Docker host networking, because containers on bridge
networks on that NAS have no outbound access at all (no DNS, no internet). The workflow
(`.gitea/workflows/deploy.yml`) runs on every push to `main` that touches `server/` or (`.gitea/workflows/deploy.yml`) runs on every push to `main` that touches `server/` or
`deploy/aws/`, or by hand from the Gitea Actions tab. One-time setup: `deploy/aws/`, or by hand from the Gitea Actions tab. One-time setup: