Gitea Actions runner for docker-1 (deploy/runner), DEPLOY.md and PLAN.md notes
ci / frontend (push) Successful in 10m18s
ci / server (push) Successful in 13m14s
ci / e2e (push) Failing after 39s
ci / image (push) Failing after 3m5s

Co-Authored-By: Claude Fable 5.1 <[email protected]>
This commit is contained in:
2026-10-16 10:05:40 -06:00
co-authored by Claude Fable 5.1
parent 37d9a0cb50
commit 0df0ea62e9
6 changed files with 136 additions and 1 deletions
+27
View File
@@ -0,0 +1,27 @@
# act_runner configuration for the docker-1 runner. Every value not set here keeps the runner's default.
# Reference: https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml
log:
level: info
job:
dir: /data/logs # a copy of each job log, kept a week
retention: 168h
runner:
file: /data/.runner
capacity: 2 # server and frontend jobs run side by side; the e2e job is heavy on its own
timeout: 1h
labels:
- "ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest"
cache:
enabled: true
dir: /data/cache
container:
# The job workspace is a Docker volume; the Docker proxy maps workspace paths for sibling
# containers, so `docker compose` in the e2e job can bind-mount tests/e2e and deploy/postgres/initdb.
privileged: false
valid_volumes: []
# The proxy removes what a job started (the CI compose stack included) when the job ends.
sweep: true