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

Deploy from a dedicated runner on Chronicles-AB
Deploy Waters Boards to AWS / deploy (push) Failing after 2m6s
Details

Browse Source 
The workflow now runs on the aws-deploy label: an act_runner container on the
Gitea NAS, registered for this repo only. The checklist app's nas runner on
Chronicles-NA is no longer involved.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
michael
2026-10-15 10:59:01 -04:00
co-authored by Claude Fable 5.1
parent aad1f40948
commit ecfb26d40a
2 changed files with 19 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+11 -8
View File
@@ -1,10 +1,12 @@
# Push to main -> Waters Boards is rebuilt on the AWS Lightsail box.
#
# Runs on the "nas" act_runner, which lives inside the church network and can reach the
# internet. (The Gitea server isn't reachable from outside, so AWS can't pull from it; the
# runner pushes to AWS instead.) It syntax-checks the code, rsyncs server/ and deploy/aws/ to
# /opt/waters-boards on the box over SSH, rebuilds in place and waits for the healthcheck.
# All of that is deploy/aws/deploy.sh, the same script you run from a laptop.
# Runs on the "aws-deploy" act_runner: a container on Chronicles-AB (the Gitea NAS) in
# /volume2/docker/gitea-runner-boards, registered for this repo only. It lives inside the
# church network because the Gitea server isn't reachable from outside, so AWS can't pull
# from it; the runner pushes to AWS instead. It syntax-checks the code, rsyncs server/ and
# deploy/aws/ to /opt/waters-boards on the box over SSH, rebuilds in place and waits for the
# 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.
#
# 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
@@ -17,8 +19,9 @@
# DEPLOY_ENABLED true
# Until DEPLOY_ENABLED is true this job is skipped, so pushes made before the box is
# ready don't show as failures.
# 4. The "nas" runner must be registered where it can see this repo (user- or instance-level,
# not only on the checklist repo).
# 4. The runner: on Chronicles-AB, /volume2/docker/gitea-runner-boards/start-runner.sh
# (re)creates it. Its runner.env holds a registration token scoped to this repo, minted
# with: docker exec -u git gitea gitea actions generate-runner-token --scope christian/waters-boards
# /opt/waters-boards/.env must already exist on the box. The deploy never creates or
# overwrites it, and never touches data/.
@@ -36,7 +39,7 @@ on:
jobs:
deploy:
if: ${{ vars.DEPLOY_ENABLED == 'true' }}
runs-on: nas
runs-on: aws-deploy
container:
image: node:22-alpine