Hartmut
b164c4ca70
CI / Architecture Guardrails (push) Has started running
CI / Typecheck (push) Has started running
CI / Lint (push) Has started running
CI / Assistant Split Regression (push) Has started running
CI / Unit Tests (push) Has been cancelled
CI / Build (push) Has been cancelled
CI / E2E Tests (push) Has been cancelled
CI / Fresh-Linux Docker Deploy (push) Has been cancelled
CI / Release Images (push) Has been cancelled
E2E: rename service hosts postgres/redis to e2epg/e2eredis — the gitea_gitea network has multiple containers answering to 'postgres' (Gitea core + concurrent job services), causing split-brain where prisma db push and db:seed connected to different databases and audit_logs ended up missing. docker-compose.ci.yml: stop attaching postgres/redis to gitea_gitea for the docker-deploy-test job — only the app needs cross-network reachability; the compose services talk to each other on the internal default network. Docker Deploy: setup-admin.mjs imports @prisma/client and @node-rs/argon2 which only live in packages/db/node_modules. Node resolves bare specifiers from the script's directory (/app/scripts), not cwd, so pnpm --filter wrappers did not help. Set NODE_PATH to packages/db/node_modules as a fallback resolution root.
31 lines
1.3 KiB
YAML
31 lines
1.3 KiB
YAML
# CI override for docker-deploy-test.
|
|
#
|
|
# The dev compose bind-mounts `.:/app` so edits are live during `pnpm dev`.
|
|
# Under act_runner (docker-outside-of-docker on Gitea), the host docker
|
|
# daemon cannot see the job container's /workspace/... path, so the bind
|
|
# mount resolves to an empty directory inside the app container and masks
|
|
# everything the Dockerfile copied in — including tooling/docker/app-dev-start.sh.
|
|
#
|
|
# Result: `sh: cannot open ./tooling/docker/app-dev-start.sh: No such file`.
|
|
#
|
|
# This override strips all bind mounts from the `app` service so the image
|
|
# runs against its baked-in copy of the repo.
|
|
services:
|
|
app:
|
|
volumes: !reset []
|
|
# Attach only the app to gitea_gitea so the act_runner job container
|
|
# (which lives on gitea_gitea) can reach the compose app by service name.
|
|
# Do NOT attach postgres/redis here — doing so causes hostname collisions
|
|
# with other containers already on gitea_gitea (Gitea core + concurrent
|
|
# job service containers all answer to "postgres"), producing split-brain
|
|
# where different clients hit different DBs. The app talks to postgres/
|
|
# redis by service name on the internal compose network, which works
|
|
# regardless of gitea_gitea.
|
|
networks:
|
|
- default
|
|
- gitea_gitea
|
|
|
|
networks:
|
|
gitea_gitea:
|
|
external: true
|