Documents the second runner and the job order
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
+10
-1
@@ -28,7 +28,16 @@ In Gitea, under **Repository → Settings → Actions**:
|
||||
| `HEALTH_CHECK_URL_PRODUCTION` | `https://andreaslop.nl/` | no; set it only once the DNS points to the new host |
|
||||
| `FTP_REMOTE_DIR` | `wwwroot` | no; default `wwwroot` |
|
||||
|
||||
Check that Actions is enabled for the repository. The global runner `raspberry-pi-arm64` picks up `runs-on: ubuntu-latest`.
|
||||
Check that Actions is enabled for the repository. Two global runners, each job image `gitea/runner-images:ubuntu-latest`. A job runs on a runner that has **all** its `runs-on` labels.
|
||||
|
||||
| Runner | Labels | Always on | Runs |
|
||||
|---|---|---|---|
|
||||
| `raspberry-pi-arm64` (systemd service `gitea-runner`, config `/etc/gitea-runner/config.yaml`) | `global`, `linux`, `arm64`, `podman`, `raspberry-pi`, plus `ubuntu-latest` and `linux-arm64` for older workflows | yes | everything |
|
||||
| `bryan-desktop-podman` (Podman machine on the owner's PC, `C:\Users\Bryan\gitea-runner\`) | `global`, `linux`, `x64`, `podman`, `bryan-desktop` | no | `check` and `lighthouse` when it is free |
|
||||
|
||||
`check` and `lighthouse` use `runs-on: linux`, the deploys `runs-on: raspberry-pi`. `deploy-test` is listed above `lighthouse` in the workflow: Gitea hands out waiting jobs in that order, so a single free runner deploys first, while two runners deploy and run Lighthouse at the same time.
|
||||
|
||||
Notes for the PC runner: its job containers share the WSL kernel, so the runner mounts an empty `/.dockerenv` (otherwise `is-wsl` in chrome-launcher treats the container as WSL and Lighthouse fails). Container actions (`uses:` of a Docker action) do not work on Podman; that is one reason deploys stay on the Pi.
|
||||
|
||||
### 1.2 Test server (Raspberry Pi with nginx)
|
||||
The current WordPress site runs on the same Pi. The test site gets its **own folder** and its **own nginx block**, and touches nothing of WordPress.
|
||||
|
||||
Reference in New Issue
Block a user