CI: workflow_dispatch-inputs en config-uitvoer met sitenaam (deploy_sls_test, deploy_sls_production, *_sls_*, artefacten app-sls-*); docs bijgewerkt

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-15 14:54:25 +01:00
co-authored by Claude Sonnet 5.5
parent d63ba28cdc
commit d1f833b556
6 changed files with 59 additions and 59 deletions
@@ -530,9 +530,9 @@ Current compact overview, including the ASF test jobs and deploying a branch: `d
Already built (U5/U6) — this is the read-only walkthrough for whoever operates it:
1. Push to `master`, or a manual `workflow_dispatch` (inputs `deploy_test`, `deploy_production`, `deploy_asf_test`, all off by default) → the gates run (`changes`, `backend-build`, `backend-test`, `vulnerability-scan`, `frontend-prepare`, `frontend-build`, `frontend-test`, `frontend-lint`)
2. `publish-sls-test` runs on a push to `master`, on pull requests (build only, no deploy) and on a dispatch with `deploy_test`; `publish-sls-production` only on a dispatch with `deploy_production`
3. `deploy-sls-test` (on a push to `master`, or a dispatch with `deploy_test`; not on pull requests) calls `deploy-scp.yaml`, which uploads into a new
1. Push to `master`, or a manual `workflow_dispatch` (inputs `deploy_sls_test`, `deploy_sls_production`, `deploy_asf_test`, all off by default) → the gates run (`changes`, `backend-build`, `backend-test`, `vulnerability-scan`, `frontend-prepare`, `frontend-build`, `frontend-test`, `frontend-lint`)
2. `publish-sls-test` runs on a push to `master`, on pull requests (build only, no deploy) and on a dispatch with `deploy_sls_test`; `publish-sls-production` only on a dispatch with `deploy_sls_production`
3. `deploy-sls-test` (on a push to `master`, or a dispatch with `deploy_sls_test`; not on pull requests) calls `deploy-scp.yaml`, which uploads into a new
`releases/{timestamp}/`, links `shared/wwwroot-web` and any `shared/modules/*.dll` in, switches
`current`, restarts `slpsoftware-test.service`, verifies `https://test.slpsoftware.nl/health`,
then prunes old releases (only test — `run_db_backup: false`)
@@ -20,7 +20,7 @@ procedure.
| Environment | Host | Domain | Trigger |
|---|---|---|---|
| Test | Raspberry Pi (`linux-arm64`) | `test.slpsoftware.nl` | Automatic on push to `master`, or any `workflow_dispatch` |
| Production | Same Pi, separate directory | `slpsoftware.nl` | Only `workflow_dispatch` with `deploy_production = true` |
| Production | Same Pi, separate directory | `slpsoftware.nl` | Only `workflow_dispatch` with `deploy_sls_production = true` |
Same physical host for both (per `infrastructure-design.md` § 1) — separated by directory,
`systemd --user` unit, and local port, never by anything the workflow manages directly.
@@ -33,7 +33,7 @@ If the defect predates the retained previous release, redeploy an **earlier comm
normal pipeline:
1. `git revert` or check out the last-known-good commit on a branch
2. Push to `master` (test) or run `workflow_dispatch` with `deploy_production: true` (production) —
2. Push to `master` (test) or run `workflow_dispatch` with `deploy_sls_production: true` (production) —
the same gates and deploy sequence run as any other deploy
3. This only works because migrations are required to be forward-compatible and non-destructive
(D-26) — redeploying an older commit's code against a database that has since had newer