fix: include prisma directory in production Docker image#33
Open
waspeer wants to merge 1 commit intoslopus:mainfrom
Open
fix: include prisma directory in production Docker image#33waspeer wants to merge 1 commit intoslopus:mainfrom
waspeer wants to merge 1 commit intoslopus:mainfrom
Conversation
The Dockerfile was missing the prisma directory in the runtime stage, which prevented database migrations from running in production deployments. This fix copies the prisma directory from the builder stage to the runner stage, enabling prisma migrate deploy to work correctly. Without this fix, deployments would fail with: 'Could not find Prisma Schema that is required for this command' Generated with [Claude Code](https://claude.ai/code) via [Happy](https://happy.engineering) Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: Happy <yesreply@happy.engineering>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Dockerfile was missing the
prismadirectory in the runtime stage, which prevented database migrations from running in production deployments.Solution
This PR adds the missing
COPYcommand to copy theprismadirectory from the builder stage to the runner stage.Impact
Without this fix, deployments fail with:
With this fix:
prisma migrate deployworks correctly in productionChanges
COPY --from=builder /app/prisma ./prismato the runtime stageTesting
Tested on Coolify deployment - migrations now run successfully without manual intervention.