Files
stacks/gitea/runner-config.yaml
T
valknar b62b9b1871 fix(gitea): revert cache workarounds, rely on CONFIG_FILE fix instead
Now that CONFIG_FILE is actually loaded by the daemon (see previous
commit), retest with the embedded cache server and default settings
instead of the dedicated cache-server/host.docker.internal workaround -
that whole setup was built to route around a config file that was
silently never being read in the first place.
2026-08-24 12:00:57 +02:00

33 lines
460 B
YAML

log:
level: info
runner:
file: .runner
capacity: 4
envs: {}
env_file: .env
timeout: 3h
insecure: false
fetch_timeout: 5s
fetch_interval: 2s
labels: []
cache:
enabled: true
dir: ""
host: ""
port: 0
external_server: ""
container:
network: ""
privileged: false
options: "-v /var/run/docker.sock:/var/run/docker.sock"
workdir_parent: ""
valid_volumes: []
docker_host: ""
force_pull: false
host:
workdir_parent: ""