d-bis/proxmox

Fork 0

Files

History

defiQUG 2138a347ac

Deploy to Phoenix / deploy (push) Has been skipped

Details

Deploy to Phoenix / deploy-atomic-swap-dapp (push) Has been skipped

Details

Deploy to Phoenix / cloudflare (push) Has been skipped

Details

Deploy to Phoenix / validate (push) Failing after 1s

Details

docs(ops): resolve act_runner template merge notes (network + Postgres)

Clarify empty container.network for services DNS and DATABASE_URL hostnames;
merge README / YAML / setup doc wording after stash apply.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-05-11 21:10:58 -07:00

config-5700-heavy.yaml

fix(ci): act_runner empty network for services; docs; bump the-order/dbis_core

2026-05-11 21:05:41 -07:00

config-5701-standard.yaml

docs(ops): resolve act_runner template merge notes (network + Postgres)

2026-05-11 21:10:58 -07:00

README.md

docs(ops): resolve act_runner template merge notes (network + Postgres)

2026-05-11 21:10:58 -07:00

README.md

Gitea act_runner config templates

File	CT	Purpose
`config-5700-heavy.yaml`	5700 (`dev-vm`)	`ubuntu-latest-heavy` — large pnpm/validation jobs
`config-5701-standard.yaml`	5701 (`gitea-runner-1`)	`ubuntu-latest` / `ubuntu-22.04` / `ubuntu-20.04` — default pool

Deploy with bash scripts/dev-vm/apply-act-runner-config.sh from the repo root (LAN). Full procedure: docs/04-configuration/GITEA_ACT_RUNNER_SETUP.md.

Networking: keep container.network empty ("" in YAML). act_runner attaches workflow services: to the same per-job Docker network as the job container. network: bridge isolates the job from service containers → Prisma P1001 even when DATABASE_URL uses postgres.

CI env: in workflows with services: postgres:, set DATABASE_URL to ...@postgres:5432/... (service id as host), not localhost.