ci: fix e2e hostname collision and docker-deploy admin seed · b164c4ca70 - CapaKraken

ci: fix e2e hostname collision and docker-deploy admin seed

CI / Architecture Guardrails (push) Has started running

Details

CI / Typecheck (push) Has started running

Details

CI / Lint (push) Has started running

Details

CI / Assistant Split Regression (push) Has started running

Details

CI / Unit Tests (push) Has been cancelled

Details

CI / Build (push) Has been cancelled

Details

CI / E2E Tests (push) Has been cancelled

Details

CI / Fresh-Linux Docker Deploy (push) Has been cancelled

Details

CI / Release Images (push) Has been cancelled

Details

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.

This commit is contained in: