fix: add backend .dockerignore and fix build stage dependencies#908
Open
Doiae9 wants to merge 1 commit into
Open
fix: add backend .dockerignore and fix build stage dependencies#908Doiae9 wants to merge 1 commit into
Doiae9 wants to merge 1 commit into
Conversation
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.
Summary of Contributions
1. Optimized Docker Build Context
backend/.dockerignore: Excluded heavy and sensitive directories/files (such asnode_modules,dist,coverage,.env*,*.log, andsrc/generated) from being sent to the Docker daemon. This significantly drops the build context size and mitigates the risk of leaking sensitive environment variables into the build layers.2. Fixed Backend Dockerfile Multi-Stage Build
builderstage to execute a fullnpm installinstead of restricting dev dependencies. This ensures that essential CLI tools required for compilation (like TypeScript and Prisma) are fully available during the build phase.COPY prisma ./prismadirective into thebuilderstage to resolve a critical build failure where the compilation script could not locate the required database schema file.--omit=devflag in the finalrunnerstage to keep the production container image as lightweight, secure, and lean as possible.