diff --git a/.gitea/workflows/continuous_integration.yaml b/.gitea/workflows/continuous_integration.yaml index 4bcefc7..8593a1f 100644 --- a/.gitea/workflows/continuous_integration.yaml +++ b/.gitea/workflows/continuous_integration.yaml @@ -22,7 +22,7 @@ on: # A new push to the same PR does not cancel an already-running CI attempt by default (each # `synchronize` event starts an independent run) — this opts in to cancelling the superseded one, -# but ONLY for pull_request events. `deploy-test`/`deploy-production` never run on a pull_request +# but ONLY for pull_request events. `deploy-sls-test`/`deploy-sls-production` never run on a pull_request # (they require a push to master or a workflow_dispatch, see those jobs' `if:` conditions), so # scoping cancel-in-progress to pull_request here can never abort a live deploy mid-flight. concurrency: @@ -31,8 +31,8 @@ concurrency: # Reusable settings for this workflow. Change these in one place if the .NET/Node/pnpm version, # artifact names, or deploy destinations change. The env context is NOT available inside a called -# reusable workflow's `with:` inputs (see the `config` job below, which works around this by passing -# these values through as job outputs to the `deploy-test` / `deploy-production` jobs). +# reusable workflow's `with:` inputs (see the `config-sls` job below, which works around this by passing +# these values through as job outputs to the `deploy-sls-test` / `deploy-sls-production` jobs). env: DOTNET_VERSION: '10.0.x' NODE_VERSION: '20' @@ -51,8 +51,8 @@ env: jobs: # Passes the env: values above through as job outputs, since the env context is unavailable in - # the `with:` block of a job that calls a reusable workflow (see deploy-test / deploy-production). - config: + # the `with:` block of a job that calls a reusable workflow (see deploy-sls-test / deploy-sls-production). + config-sls: runs-on: linux outputs: artifact_name_test: ${{ steps.set.outputs.artifact_name_test }} @@ -258,7 +258,7 @@ jobs: # --- Gate 4: frontend build --- # Validates the frontend compiles on its own, independent of any environment. The actual # per-environment deployable artifact is produced later by each publish job's own "Build admin - # frontend" step (publish-test / publish-production, below), which builds frontend/ again with + # frontend" step (publish-sls-test / publish-sls-production, below), which builds frontend/ again with # that environment's Vite variables set and copies the result into wwwroot/admin before # `dotnet publish` runs — see that step's comment for why this isn't an MSBuild target instead. frontend-build: @@ -356,7 +356,7 @@ jobs: # kept in sync with the host's real SecurityHeaders__AllowedScriptOrigins__0 env var (D-16). This # gate cannot see the actual runtime CSP configuration; it only catches drift between the frontend # build and what this variable claims the CSP allows. - publish-test: + publish-sls-test: needs: [changes, backend-build, backend-test, vulnerability-scan, frontend-build, frontend-test, frontend-lint] # always() bypasses the automatic skip-cascade from a gate job that was itself skipped (because # its side of the repo didn't change). Gitea Actions only implements always() from the GitHub @@ -437,12 +437,12 @@ jobs: path: ${{ env.ARTIFACT_NAME_TEST }} retention-days: 1 - # Same as publish-test, but only for a manual workflow_dispatch run with deploy_production set — - # a distinct job rather than a parameterized reuse of publish-test, because VITE_APP_ENV is a + # Same as publish-sls-test, but only for a manual workflow_dispatch run with deploy_production set — + # a distinct job rather than a parameterized reuse of publish-sls-test, because VITE_APP_ENV is a # Vite build-time value: one dist/ bundle cannot be tagged as both 'test' and 'production' (FR-05). - publish-production: + publish-sls-production: needs: [changes, backend-build, backend-test, vulnerability-scan, frontend-build, frontend-test, frontend-lint] - # See publish-test's comment above on why this checks needs..result explicitly instead of + # See publish-sls-test's comment above on why this checks needs..result explicitly instead of # failure()/cancelled(), which Gitea Actions doesn't support. if: | always() && @@ -478,7 +478,7 @@ jobs: exit 1 fi - # See publish-test's "Build admin frontend" step for why this runs as its own step ahead of + # See publish-sls-test's "Build admin frontend" step for why this runs as its own step ahead of # dotnet publish rather than an MSBuild target. - name: Build admin frontend working-directory: frontend @@ -512,18 +512,18 @@ jobs: # extra steps). A manual workflow_dispatch run only deploys to test when deploy_test is checked, # since a dispatch run is often just re-running CI/production, not a new test build (FR-03, D-01, # D-09). - # deploy_path / service_name / health_check_url come straight from the Gitea variables, NOT from the `config` job + # deploy_path / service_name / health_check_url come straight from the Gitea variables, NOT from the `config-sls` job # outputs: a job output whose value contains a secret value (here most likely the deploy account name inside the # path) is dropped by the runner, so the reusable workflow received an empty deploy_path ("/releases"). The - # `config` outputs are still used for the artifact and environment names. - deploy-test: - needs: [publish-test, config] + # `config-sls` outputs are still used for the artifact and environment names. + deploy-sls-test: + needs: [publish-sls-test, config-sls] if: (github.event_name == 'workflow_dispatch' && github.event.inputs.deploy_test == 'true') || (github.event_name == 'push' && github.ref == 'refs/heads/master') uses: ./.gitea/workflows/deploy-scp.yaml secrets: inherit with: - artifact_name: ${{ needs.config.outputs.artifact_name_test }} - environment: ${{ needs.config.outputs.deploy_environment_test }} + artifact_name: ${{ needs.config-sls.outputs.artifact_name_test }} + environment: ${{ needs.config-sls.outputs.deploy_environment_test }} deploy_path: ${{ vars.DEPLOY_PATH_TEST }} service_name: ${{ vars.SERVICE_NAME_TEST }} health_check_url: ${{ vars.HEALTH_CHECK_URL_TEST }} @@ -532,14 +532,14 @@ jobs: # Production deploy ONLY on an explicit workflow_dispatch run with deploy_production checked # (FR-04, D-09) — never reachable from a plain push to master, so pushing cannot deploy production # under any circumstance. - deploy-production: - needs: [publish-production, config] + deploy-sls-production: + needs: [publish-sls-production, config-sls] if: github.event_name == 'workflow_dispatch' && github.event.inputs.deploy_production == 'true' uses: ./.gitea/workflows/deploy-scp.yaml secrets: inherit with: - artifact_name: ${{ needs.config.outputs.artifact_name_production }} - environment: ${{ needs.config.outputs.deploy_environment_production }} + artifact_name: ${{ needs.config-sls.outputs.artifact_name_production }} + environment: ${{ needs.config-sls.outputs.deploy_environment_production }} deploy_path: ${{ vars.DEPLOY_PATH_PRODUCTION }} service_name: ${{ vars.SERVICE_NAME_PRODUCTION }} health_check_url: ${{ vars.HEALTH_CHECK_URL_PRODUCTION }} @@ -583,7 +583,7 @@ jobs: publish-asf-test: needs: [changes, backend-build, backend-test, vulnerability-scan, frontend-build, frontend-test, frontend-lint] - # Same gate handling as publish-test (see there for why always() and explicit results), plus the + # Same gate handling as publish-sls-test (see there for why always() and explicit results), plus the # ASF switch, and built only when it will actually be deployed. if: | always() && @@ -612,7 +612,7 @@ jobs: version: ${{ env.PNPM_VERSION }} # Admin SPA with the ASF theme and Dutch as the default language. Lands in wwwroot/admin - # BEFORE dotnet publish, for the same reason as in publish-test. No Umami for the admin. + # BEFORE dotnet publish, for the same reason as in publish-sls-test. No Umami for the admin. - name: Build admin frontend (ASF theme) working-directory: frontend env: @@ -640,7 +640,7 @@ jobs: path: app-asf-test retention-days: 1 - # Path/service/health straight from the Gitea variables, like deploy-test (a job output containing a secret value, + # Path/service/health straight from the Gitea variables, like deploy-sls-test (a job output containing a secret value, # here the deploy account name in the path, arrives empty). config-asf still validates that they are set. deploy-asf-test: needs: [publish-asf-test, config-asf] diff --git a/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md b/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md index ae872ad..96909e7 100644 --- a/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md +++ b/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md @@ -402,14 +402,14 @@ server { } ``` -#### 1.7.3 Artifact Upload Body Size (413 on `publish-test`/`publish-production`) +#### 1.7.3 Artifact Upload Body Size (413 on `publish-sls-test`/`publish-sls-production`) The Gitea instance itself (`gitea.slpsoftware.nl`) sits behind the same proxy Pi as every other domain in § 1.7 — Actions' own web UI/API traffic is proxied through it exactly like `test.slpsoftware.nl` and `slpsoftware.nl` are. Gitea Actions' artifact upload (`actions/upload-artifact`) sends the build output in chunks; if a chunk exceeds nginx's `client_max_body_size` (default 1m), nginx itself rejects it with `413 Request Entity Too Large` -before the request ever reaches Gitea — surfacing in the `publish-test`/`publish-production` job log +before the request ever reaches Gitea — surfacing in the `publish-sls-test`/`publish-sls-production` job log as repeated `A 413 status code has been received, will attempt to retry the upload` followed by `Retry limit has been reached` on individual files once the action's retries are exhausted. @@ -433,9 +433,9 @@ http { sudo nginx -t && sudo systemctl reload nginx ``` -#### 1.7.4 Never Re-Run `deploy-test`/`deploy-production` Alone — Gitea Platform Limitation +#### 1.7.4 Never Re-Run `deploy-sls-test`/`deploy-sls-production` Alone — Gitea Platform Limitation -`deploy-test` and `deploy-production` in `continuous_integration.yaml` are not ordinary jobs — each +`deploy-sls-test` and `deploy-sls-production` in `continuous_integration.yaml` are not ordinary jobs — each one *calls* the reusable `deploy-scp.yaml` workflow (`uses: ./.gitea/workflows/deploy-scp.yaml`). Re-running **only** one of these two jobs after a failure (Gitea's per-job "re-run" action) is a known Gitea Actions limitation, not a bug in either workflow file here: Gitea does not cleanly resume @@ -446,7 +446,7 @@ List Artifacts - Error is not retryable Status Code: 404 Error: List Artifacts failed: Artifact service responded with 404 ``` -even though `publish-test`/`publish-production` genuinely succeeded and uploaded the artifact +even though `publish-sls-test`/`publish-sls-production` genuinely succeeded and uploaded the artifact moments earlier in the same run (retention had not expired — this is not the same failure mode as § 1.7.3, and not a retention issue at all). @@ -466,13 +466,13 @@ This matches a documented behaviour of Actions-style re-run implementations, see GitHub's own tooling ([cli/cli#13522](https://github.com/cli/cli/issues/13522)): re-running an *existing* run can replay against secrets/variables as they were **when that run was first created**, not their current values — particularly for a job that calls a reusable workflow with -`secrets: inherit` (exactly what `deploy-test`/`deploy-production` do here). The documented contract +`secrets: inherit` (exactly what `deploy-sls-test`/`deploy-sls-production` do here). The documented contract ("secrets are fetched at the time of the re-run") does not hold in practice for this case. A genuinely **new** run (fresh push, or `workflow_dispatch`) always fetches current values correctly — only re-running an existing run risks the stale snapshot. **Net effect of § 1.7.4 + § 1.7.5 together**: neither of Gitea's two "re-run" options is fully safe -for `deploy-test`/`deploy-production` — "re-run this job alone" loses the artifact, "re-run all jobs" +for `deploy-sls-test`/`deploy-sls-production` — "re-run this job alone" loses the artifact, "re-run all jobs" can keep stale secrets. **The one reliable option is to trigger a brand new run** (an actual push, or `workflow_dispatch`'s "Run workflow" button) rather than using either re-run action on a failed run, whenever a secret or variable was just changed to fix that failure. Re-running an existing run is @@ -531,12 +531,12 @@ 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-test` runs on a push to `master`, on pull requests (build only, no deploy) and on a dispatch with `deploy_test`; `publish-production` only on a dispatch with `deploy_production` -3. `deploy-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 +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 `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`) -4. `deploy-production` (only with the flag) does the same, plus a database backup first +4. `deploy-sls-production` (only with the flag) does the same, plus a database backup first (`run_db_backup: true`) — see § 4 ## 3. First-Ever Deploy Notes @@ -634,7 +634,7 @@ section documents what actually changes when that day comes (OPEN-04 — not sch per Q5 = B of the deployment setup plan). ### 5.1 What carries over unchanged -- The CI workflow's gates, the two-build split, the `config` job pattern +- The CI workflow's gates, the two-build split, the `config-sls` job pattern - The overall shape of the interface: `artifact_name`, `environment`, `deploy_path` ### 5.2 What does not carry over — read this before assuming it's a drop-in swap diff --git a/aidlc-docs/features/gitea-deployment-workflow/operations/monitoring/monitoring-instructions.md b/aidlc-docs/features/gitea-deployment-workflow/operations/monitoring/monitoring-instructions.md index e8c91e4..db66621 100644 --- a/aidlc-docs/features/gitea-deployment-workflow/operations/monitoring/monitoring-instructions.md +++ b/aidlc-docs/features/gitea-deployment-workflow/operations/monitoring/monitoring-instructions.md @@ -25,7 +25,7 @@ there is no separate DSN per environment. | Variable | Value | |---|---| -| `VITE_SENTRY_DSN` | the project's DSN (same value used by both `publish-test` and `publish-production`) | +| `VITE_SENTRY_DSN` | the project's DSN (same value used by both `publish-sls-test` and `publish-sls-production`) | ### 1.2 Host configuration diff --git a/aidlc-docs/features/slpsoftware-api/operations/deployment/deployment-instructions.md b/aidlc-docs/features/slpsoftware-api/operations/deployment/deployment-instructions.md index 645b403..68854e3 100644 --- a/aidlc-docs/features/slpsoftware-api/operations/deployment/deployment-instructions.md +++ b/aidlc-docs/features/slpsoftware-api/operations/deployment/deployment-instructions.md @@ -14,7 +14,7 @@ as the artifact built, tested, and deployed to `test.slpsoftware.nl` / `slpsoftw | File | Change | |---|---| -| `.gitea/workflows/continuous_integration.yaml` | `publish-test`/`publish-production`'s "Build admin frontend" and "Publish" steps retargeted from `src/SlpModularCms.Api` to `src/SlpModularCms.Api.SlpSoftware` (6 lines). Everything else — the six CI gates, `deploy-scp.yaml` calls, Gitea variables/secrets, `SlpModularCms.Api.Tests` (Unit 1's own regression suite, scoped to `Api` per NFR-CS-01) — is unchanged. | +| `.gitea/workflows/continuous_integration.yaml` | `publish-sls-test`/`publish-sls-production`'s "Build admin frontend" and "Publish" steps retargeted from `src/SlpModularCms.Api` to `src/SlpModularCms.Api.SlpSoftware` (6 lines). Everything else — the six CI gates, `deploy-scp.yaml` calls, Gitea variables/secrets, `SlpModularCms.Api.Tests` (Unit 1's own regression suite, scoped to `Api` per NFR-CS-01) — is unchanged. | | `deploy-scp.yaml` | **No change.** It never hardcodes an entry-point `.dll` name; it uploads whatever the artifact contains and restarts a `service_name` input string. | | `gitea-deployment-workflow/operations/deployment/deployment-instructions.md` § 1.6 | systemd unit `ExecStart` documentation updated to `SlpModularCms.Api.SlpSoftware.dll`, with an explicit note that this is a manual, host-side edit for already-existing units — this session cannot reach the Pi to apply it. | | `rollback-plan.md` | **No change.** Operates on the release-directory/symlink level, not a specific `.dll` name. | diff --git a/docs/cms-themas.md b/docs/cms-themas.md index 78635c9..770cf42 100644 --- a/docs/cms-themas.md +++ b/docs/cms-themas.md @@ -21,7 +21,7 @@ Code: `frontend/themes/resolveTheme.ts` (met tests), `frontend/vite.config.ts`, | Site | Build | Thema | |---|---|---| -| SLP Software | publish-test en publish-production in `.gitea/workflows/continuous_integration.yaml` | `slpsoftware`, titel `SLP Software` | +| SLP Software | publish-sls-test en publish-sls-production in `.gitea/workflows/continuous_integration.yaml` | `slpsoftware`, titel `SLP Software` | | Andrea Slop Fotografie | stap "Build admin frontend (ASF theme)" | `asf`, taal `nl` | | Andere hosts | geen `VITE_THEME` | standaardadmin | diff --git a/docs/deploy-en-testomgevingen.md b/docs/deploy-en-testomgevingen.md index b04a5cb..472c69f 100644 --- a/docs/deploy-en-testomgevingen.md +++ b/docs/deploy-en-testomgevingen.md @@ -6,8 +6,8 @@ Compact overzicht van hoe code op de testomgevingen en productie komt. Bron: `.g | Omgeving | Wat | Publieke URL en health | Deploy-job | |---|---|---|---| -| SlpSoftware test | `SlpModularCms.Api.SlpSoftware` | `https://test.slpsoftware.nl`, health `https://test.slpsoftware.nl/health` | `deploy-test` | -| SlpSoftware productie | `SlpModularCms.Api.SlpSoftware` | `https://slpsoftware.nl`, health `https://slpsoftware.nl/health` | `deploy-production` | +| SlpSoftware test | `SlpModularCms.Api.SlpSoftware` | `https://test.slpsoftware.nl`, health `https://test.slpsoftware.nl/health` | `deploy-sls-test` | +| SlpSoftware productie | `SlpModularCms.Api.SlpSoftware` | `https://slpsoftware.nl`, health `https://slpsoftware.nl/health` | `deploy-sls-production` | | ASF test (Andrea Slop Fotografie) | `SlpModularCms.Api.AndreaSlopFotografie` (website + admin met thema `asf`) | `https://test.andreaslop.nl`, health `https://test.andreaslop.nl/health` | `deploy-asf-test` | De werkelijke health-URL's komen uit de Gitea-variabelen `HEALTH_CHECK_URL_TEST`, `HEALTH_CHECK_URL_PRODUCTION` en `HEALTH_CHECK_URL_ASF_TEST`; de waarden staan niet in de repository. De hostnamen hierboven komen uit de feature-documentatie (`deployment-instructions.md` van `gitea-deployment-workflow` en `andreaslop-site-hosting`) en zijn niet uit de workflows zelf af te leiden. Er is geen productie-deploy voor ASF in deze pipeline (de ASF-productie draait apart op IIS, zie `aidlc-docs/active-features.md`). @@ -16,8 +16,8 @@ De werkelijke health-URL's komen uit de Gitea-variabelen `HEALTH_CHECK_URL_TEST` | Trigger | Wat er gebeurt | |---|---| -| `pull_request` (opened, synchronize, reopened) | De poorten (build, tests, kwetsbaarheidscontrole, frontend build/test/lint) en daarna `publish-test`: bouwt een testartefact. Er wordt **niet** gedeployed. Een nieuwe push naar dezelfde PR annuleert de lopende run (alleen bij PR's). | -| `push` op `master` | Dezelfde poorten, daarna automatisch `deploy-test` (SlpSoftware test) en, als `ASF_TEST_DEPLOY_ENABLED` op `true` staat, ook `deploy-asf-test`. Nooit productie. | +| `pull_request` (opened, synchronize, reopened) | De poorten (build, tests, kwetsbaarheidscontrole, frontend build/test/lint) en daarna `publish-sls-test`: bouwt een testartefact. Er wordt **niet** gedeployed. Een nieuwe push naar dezelfde PR annuleert de lopende run (alleen bij PR's). | +| `push` op `master` | Dezelfde poorten, daarna automatisch `deploy-sls-test` (SlpSoftware test) en, als `ASF_TEST_DEPLOY_ENABLED` op `true` staat, ook `deploy-asf-test`. Nooit productie. | | `workflow_dispatch` (handmatig, op elke gekozen branch) | Alle poorten draaien altijd volledig (het pad-filter meldt dan backend en frontend als gewijzigd). Deployen gebeurt alleen voor de aangevinkte invoer, zie hieronder. | Poorten (jobs): `changes` (pad-filter), `backend-build`, `backend-test` (met een MariaDB-servicecontainer op poort 3308), `vulnerability-scan`, `frontend-prepare`, `frontend-build`, `frontend-test`, `frontend-lint`. Een poort die overgeslagen is (omdat die kant van de repo niet wijzigde) blokkeert niet; een poort die faalt of wordt geannuleerd blokkeert elke publish. Pad-filter bij push/PR: backend = `src/**`, `tests/**`, `*.sln`, `**/*.csproj` en de workflowbestanden; frontend = `frontend/**` en de workflowbestanden. Een run die geen van beide raakt publiceert niets. @@ -26,11 +26,17 @@ Poorten (jobs): `changes` (pad-filter), `backend-build`, `backend-test` (met een | Invoer | Standaard | Effect | |---|---|---| -| `deploy_test` | uit | Bouwt (`publish-test`) en deployt naar SlpSoftware test | -| `deploy_production` | uit | Bouwt (`publish-production`) en deployt naar SlpSoftware productie, met databaseback-up vooraf | +| `deploy_test` | uit | Bouwt (`publish-sls-test`) en deployt naar SlpSoftware test | +| `deploy_production` | uit | Bouwt (`publish-sls-production`) en deployt naar SlpSoftware productie, met databaseback-up vooraf | | `deploy_asf_test` | uit | Bouwt (`publish-asf-test`) en deployt naar ASF test; alleen als ook `ASF_TEST_DEPLOY_ENABLED` op `true` staat | -Zonder een van de drie aangevinkt draaien alleen de poorten (handig als losse CI-run). Meerdere tegelijk aanvinken kan. Let op: `deploy_production` is aan de `master`-branch niet gebonden in de workflow: de conditie van `deploy-production` controleert alleen de gebeurtenis en de invoer, niet de branch (zie `ci`, job `deploy-production`). +Zonder een van de drie aangevinkt draaien alleen de poorten (handig als losse CI-run). Meerdere tegelijk aanvinken kan. Let op: `deploy_production` is aan de `master`-branch niet gebonden in de workflow: de conditie van `deploy-sls-production` controleert alleen de gebeurtenis en de invoer, niet de branch (zie `ci`, job `deploy-sls-production`). + +## Jobnamen en branch protection (merge-checklist) + +Jobnamen volgen `{actie}-{site}-{omgeving}`: `config-sls`, `publish-sls-test`, `deploy-sls-test`, `publish-sls-production`, `deploy-sls-production` en voor Andrea `config-asf`, `publish-asf-test`, `deploy-asf-test`. De invoeren van de handmatige run (`deploy_test`, `deploy_production`, `deploy_asf_test`) hebben niet van naam gewisseld. + +Branch protection op `master` vereist de checks `Continuous Integration / backend-test (pull_request)`, `frontend-test (pull_request)` en een publish-check. **Die derde check heette vroeger `publish-test (pull_request)` en moet nu `publish-sls-test (pull_request)` heten** (Gitea: repository, Instellingen, Branches, beschermde branch `master`, vereiste statuschecks). Pas dat vlak voor de merge aan, met Bryans go; tot dan zou een merge wachten op een check die niet meer bestaat. ## Een branch naar test deployen @@ -80,14 +86,14 @@ Variabelen: | Naam | Voor | |---|---| -| `DEPLOY_PATH_TEST`, `SERVICE_NAME_TEST`, `HEALTH_CHECK_URL_TEST` | SlpSoftware test. De `config`-job faalt als een van deze drie leeg is (dat geldt voor elke run, ook een PR) | +| `DEPLOY_PATH_TEST`, `SERVICE_NAME_TEST`, `HEALTH_CHECK_URL_TEST` | SlpSoftware test. De `config-sls`-job faalt als een van deze drie leeg is (dat geldt voor elke run, ook een PR) | | `DEPLOY_PATH_PRODUCTION`, `SERVICE_NAME_PRODUCTION`, `HEALTH_CHECK_URL_PRODUCTION` | SlpSoftware productie | | `ASF_TEST_DEPLOY_ENABLED` | Schakelaar voor alle ASF-jobs; alleen de waarde `true` zet ze aan | | `DEPLOY_PATH_ASF_TEST`, `SERVICE_NAME_ASF_TEST`, `HEALTH_CHECK_URL_ASF_TEST` | ASF test; `config-asf` faalt als er een leeg is (terwijl de schakelaar aan staat) | | `VITE_SENTRY_DSN` | Sentry-DSN voor de SlpSoftware-adminbuild (test en productie) | | `VITE_SENTRY_DSN_ASF` | Sentry-DSN voor de ASF-adminbuild | | `VITE_UMAMI_SCRIPT_URL`, `VITE_UMAMI_WEBSITE_ID_TEST`, `VITE_UMAMI_WEBSITE_ID_PRODUCTION` | Umami voor de SlpSoftware-adminbuild (ASF gebruikt geen Umami) | -| `SECURITY_ALLOWED_SCRIPT_ORIGINS_TEST`, `SECURITY_ALLOWED_SCRIPT_ORIGINS_PRODUCTION` | Alleen gebruikt als controle in `publish-test`/`publish-production` wanneer `VITE_UMAMI_SCRIPT_URL` gevuld is: de Umami-origin moet in deze lijst staan, en de lijst moet overeenkomen met `SecurityHeaders__AllowedScriptOrigins__0` op de host | +| `SECURITY_ALLOWED_SCRIPT_ORIGINS_TEST`, `SECURITY_ALLOWED_SCRIPT_ORIGINS_PRODUCTION` | Alleen gebruikt als controle in `publish-sls-test`/`publish-sls-production` wanneer `VITE_UMAMI_SCRIPT_URL` gevuld is: de Umami-origin moet in deze lijst staan, en de lijst moet overeenkomen met `SecurityHeaders__AllowedScriptOrigins__0` op de host | Runtime-instellingen van de applicatie (verbindingsstring, JWT, mail, `Contact__*`, Sentry) zitten niet in de workflow maar in het omgevingsbestand op de host (`shared/env`, zie README en de hostdocumentatie).