Samir Boulahtit
c93346f8ff
Some checks failed
CI / docs (push) Blocked by required conditions
CI / deploy (push) Blocked by required conditions
CI / ruff (push) Successful in 2m7s
CI / validate (push) Successful in 39s
CI / dependency-scanning (push) Successful in 45s
CI / pytest (push) Failing after 3h3m22s
Document two ways to take CI/Gitea load off the production box, since the HostHighCpuUsage floods are caused by act_runner running ruff/pytest/validate on the prod server (not by Gitea hosting, which is light): - 2a "Offloading CI to a Separate Server" — move just the act_runner to a cheap x86 box (no data migration, no DNS, no downtime). Includes the smaller build-burst caveat (deploy still builds on prod) + the registry-pull path. - 2c "Migrating Gitea to a Separate Server" — full separation runbook: pg_dump + data-volume tar/restore, DNS cutover, Caddy/SSL, rollback. Notes the box becomes stateful/critical (backups + hardening). mkdocs --strict clean; arch validation 0 new findings. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>