Files
AndreaSlopFotografie/docs/deploy-and-ci.md
T
SluijsensandClaude Sonnet 5.5 6ff415e1bc Documents the CMS packages, banners, deploy flow and go-live conditions
Adds docs/cms-integration.md, docs/deploy-and-ci.md and
docs/go-live-checklist.md, fills in the README (set-up and commands) and
points AGENTS.md at the docs so they are kept up to date.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-15 00:07:51 +01:00

4.9 KiB

Deploy and CI

Pipeline: .gitea/workflows/continuous_integration.yaml. Branch strategy and rollback are in aidlc-docs/features/frontend-shell/operations/deployment/ and aidlc-docs/features/prerendering/.

Triggers

Trigger Result
Pull request Checks only, no deploy.
Push to master Checks, then deploy to test.
Every night, 03:15 UTC (schedule) Test build with the packages and banners from the test CMS, deploy to test, no Lighthouse. Gitea runs schedules only from the default branch, so this works after the packages feature is merged to master. Never production.
Manual (workflow_dispatch), any branch Checks, and a deploy to test if deploy_test is on.
Manual from a release/* branch Deploy to production if deploy_production is on.

Workflow inputs

  • deploy_test (boolean, default false): "Deploy to Test". Builds the test artifact and deploys it to ASF test.
  • deploy_production (boolean, default false): "Deploy to Production". Only works from a release/* branch and only with Bryan's explicit go.

Dispatch from the CLI (the token comes from your git credentials, never print it): POST /api/v1/repos/SLP_Software/AndreaSlopFotografie/actions/workflows/continuous_integration.yaml/dispatches with {"ref": "<branch>", "inputs": {"deploy_test": "true"}}.

Jobs

  1. check: lint, format, unit/property/axe tests (coverage threshold 100% on src/lib/**), build without OFFERINGS_URL (so with the committed snapshot), audit. Uploads artifact dist (this is what production gets).
  2. build-test: builds again with OFFERINGS_URL=${{ vars.ASF_OFFERINGS_URL_TEST }} (packages and banners from the test CMS) and uploads dist-test.
  3. deploy-test: needs check and build-test, downloads dist-test, uploads to the ASF test host and runs the deployment check (served by the CMS host, admin files, POST status).
  4. lighthouse: against the built site with the preview stub (--audit-route --contact-stub); skipped on schedule.
  5. deploy-production: manual, from release/* only, uses artifact dist.

There is one Raspberry Pi runner plus a desktop runner, so jobs can wait in the queue for a long time (for example 30 minutes before build-test); a deploy that only just started is not hung. Check started_at (UTC) before cancelling anything.

Deploying a feature branch to test

Committing, pushing and deploying a feature branch to test is allowed for the sessions that work on it. Merging, deploying to production and changing repo variables are not (Bryan decides). After a test deploy, check the page in a real browser against the real test CMS; web/e2e/ holds the checks that run in CI.

TEST ONLY commit (must go before the merge)

feature/contact-form-cms carries commit d449e76 "TEST ONLY: enable the contact form for the ASF test deploy", which sets contactForm.enabled: true in web/src/content/siteContent.ts so the ASF test host shows the real form. It must not reach master (the form stays off in production until Bryan gives an explicit go). Before merging, revert it (git revert d449e76, or drop it from the branch) and confirm enabled is false again. The packages branch is based on the contact-form branch, so the merge order is contact-form-cms first, then asf-packages-cms. Both merges need Bryan's go.

Generated files

web/deploy/iis/web.config and web/deploy/nginx/*.conf are generated by pnpm server-config from web/config/serverConfig.ts. Change the generator, rerun it and commit the result; a test checks that they match.