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
---