Documents how the PC runner gets preference over the Pi
Continuous Integration / check (pull_request) Successful in 57s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 3m45s
Continuous Integration / deploy-production (pull_request) Skipped

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 17:22:43 +02:00
co-authored by Claude Opus 5.5
parent c24f629869
commit 0ddaaa2cb1
2 changed files with 21 additions and 0 deletions
@@ -988,3 +988,15 @@ Verder heb ik de vraag ook beantwoord"
**Context**: Feature complete; commit/push on request
---
## Deployment - Runner Preference
**Timestamp**: 2026-10-19T15:22:43Z
**User Input**: "lighthouse is weer met de raspberry pi opgepakt. kan je voorkeur geven voor runner of is het gewoon net welke hem oppakt?" / "kan jij dat nog toevoegen committen en pushen?"
**AI Response**: "Explained: Gitea has no runner priority; the first runner that fetches with matching labels gets the job, and a runner fetches again right after finishing one (run 541: check and then lighthouse on the Pi). The PC runner v3.5 also backs off to 5 s while idle. Set the PC runner to fetch_interval 1s / fetch_interval_max 1s (restarted); the Pi needs fetch_interval: 10s in /etc/gitea-runner/config.yaml (owner, outside the repo). Run 541 (c24f629) green. Documented the preference in deployment-instructions 1.1; committing and pushing on request."
**Context**: Feature complete; deployment documentation update
---
@@ -37,6 +37,15 @@ Check that Actions is enabled for the repository. Two global runners, each job i
`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.
Gitea has no runner priority: a job goes to the first runner that asks for work and has all its labels, and a runner asks again right after finishing a job. To let the PC take `check` and `lighthouse` when it is on, the PC asks every second and the Pi every 10 seconds:
| Runner | Setting under `runner:` |
|---|---|
| PC (`C:\Users\Bryan\gitea-runner\config.yaml`) | `fetch_interval: 1s` and `fetch_interval_max: 1s` (no slowing down while idle) |
| Pi (`/etc/gitea-runner/config.yaml`) | `fetch_interval: 10s`; restart with `sudo systemctl restart gitea-runner` only while it runs no job |
This is a strong preference, not a guarantee: a busy PC leaves the job to the Pi, and with the PC off the Pi starts a run at most 10 seconds later.
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)