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>
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>
Adds watersmedia.org, timhatchlive.com, waterschurchnorwood.org,
watersacademy.org and waterselc.com to the ALLOWED_DOMAINS example,
matching the live box.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Prompts for the OAuth client ID, writes it to /opt/waters-boards/.env,
recreates the app container and prints the sign-in config it reports.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Replace the planned Synology deploy with one Lightsail box: Caddy in front of the
app for automatic HTTPS (deploy/aws/docker-compose.yml, Caddyfile), a deploy
script that rsyncs server/ and rebuilds in place without touching data/ or .env,
and a Gitea workflow that runs the same script from the nas runner over SSH.
README documents the box, DNS, .env, deploys and restore. Allow both church
Google Workspace domains to sign in. Drop the NAS-only compose file.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Boards with groups, items, subitems and 18 column types; table, kanban,
calendar, timeline, chart and files views; updates with @mentions,
replies and attachments; inbox, My work, search, automations; Google
sign-in restricted to company domains; live updates over SSE; a
monday.com API importer; phone layout and installable PWA; Docker +
Gitea Actions deploy to the NAS.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
michaelandClaude Fable 5.1
christianandClaude Opus 5.5