fix(orchestrator): local prisma schema copy for Docker generate #706

jason.woltje · 2026-03-07T16:00:05Z

jason.woltje commented

2026-03-07 16:00:05 +00:00

Prisma was climbing to /app/apps/ (no package.json) when invoked cross-package. Fix: copy schema directly into apps/orchestrator/prisma/ and run generate from within the orchestrator package.

Supersedes the approach in PRs #703, #704, #705.

Prisma was climbing to /app/apps/ (no package.json) when invoked cross-package. Fix: copy schema directly into apps/orchestrator/prisma/ and run generate from within the orchestrator package. Supersedes the approach in PRs #703, #704, #705.

jason.woltje added 1 commit 2026-03-07 16:00:06 +00:00

fix(orchestrator): copy schema into orchestrator/prisma/ for local prisma generate

ci/woodpecker/push/ci Pipeline failed

Details

b5007885ad

Prisma was climbing the directory tree to find a project root and landing at
/app/apps/ which has no package.json. Fix: copy the API schema directly into
apps/orchestrator/prisma/schema.prisma and run generate from within the
orchestrator package context using node_modules/.bin/prisma directly.

This keeps prisma generate fully self-contained within the orchestrator package
and avoids all cross-package project-root detection issues.

jason.woltje merged commit 977747599f into main

2026-03-07 16:00:08 +00:00

jason.woltje referenced this issue from a commit

2026-03-07 16:00:10 +00:00

fix(orchestrator): local prisma schema copy for Docker generate (#706)

jason.woltje referenced this pull request

2026-03-07 16:17:17 +00:00

fix(orchestrator): symlink prisma/schema.prisma to resolve Docker build root detection #707

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaic/stack#706