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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user