Documenteer CI-proef run 606/607 en gevolgen van ASF_TEST_DEPLOY_ENABLED
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
+5
@@ -12,6 +12,11 @@ Verify prerequisites, create database/user, directories + symlink `shared/wwwroo
|
||||
## 2. Cut over (phase B, accepted short test downtime)
|
||||
Save the current proxy block; verify the three forwarded headers are present; change only `proxy_pass` to `http://192.168.1.103:5200`; test config; reload. Set `ASF_TEST_DEPLOY_ENABLED=true`; push to master or run the workflow manually with "Deploy ASF test".
|
||||
|
||||
## 2b. Consequences of the switch being `true` (verified on Gitea, run 606/607)
|
||||
- `vars.ASF_TEST_DEPLOY_ENABLED == 'true'` in a job-level `if:` works on this Gitea (`config-asf` ran with the variable set).
|
||||
- With the variable `true`, **a push or merge to master now deploys ASF test** (besides SlpSoftware test).
|
||||
- The first ASF deploy does **not** need a merge: run "Continuous Integration" manually on the branch `feature/andreaslop-site-hosting` with only "Deploy ASF test" ticked (`deploy-asf-test` accepts any ref on dispatch). A dispatch with all boxes unticked builds and tests only (runs 606/607) and deploys nothing.
|
||||
|
||||
## 3. What a deploy does (every time)
|
||||
Build admin (`VITE_THEME=asf`, Dutch default) -> publish linux-arm64 -> upload to `releases/<timestamp>` -> link `wwwroot/web` to `shared/wwwroot-web` -> atomic switch of `current` -> `systemctl --user restart` -> `/health` on the public URL (10 tries) -> prune to current + previous.
|
||||
|
||||
|
||||
+1
-1
@@ -26,7 +26,7 @@ Scope: the TEST environment `test.andreaslop.nl`. Production is out of scope; it
|
||||
## Overall Readiness
|
||||
- **Ready for Production**: Not applicable to production. For TEST: Yes with caveats (below).
|
||||
- **Open Follow-ups**:
|
||||
1. CI proof pending: Bryan starts `workflow_dispatch` on the branch (deploy boxes unticked); `backend-test` (MariaDB: `Api.Tests`, ASF `HostPipelineTests`), frontend and vulnerability scan must be green.
|
||||
1. CI proof: DONE. Run 607 (branch, head e37b8f3, dispatch, no deploy) is fully green incl. backend-test with MariaDB (`Api.Tests`, ASF `HostPipelineTests`), frontend and vulnerability scan. Run 606 had one cold-start timing failure in the first `SetupPage` test (flake, same commit passed in 607). Optional: harden that test.
|
||||
2. First test deploy not done (needs the explicit go from CMS & API/Bryan; Pi preparation reported done, proxy route already switched, `ASF_TEST_DEPLOY_ENABLED` unset).
|
||||
3. After the first deploy: verification list (manual steps 14-18), forwarded-header observation, optional Pi timing, remove the setup token, report in the hand-back.
|
||||
4. Sentry alert rules to be created after the first successful deploy (by the CMS & API session, with Bryan's go).
|
||||
|
||||
Reference in New Issue
Block a user