Repository navigation
Optimize Docker build and harden production image - #1391
Merged
Merged
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.
The previous production build inherited development tooling, repeated dependency installation and Prisma generation, and admitted local secrets into its build context. Separate the build stages, cache npm downloads, prune development dependencies, and copy only runtime files.
Keep Node 22 and Debian Bookworm consistent across stages, pin PM2, install OpenSSL explicitly, and run production as the node user with writable runtime assets. Preserve startup migrations and command registration behavior.
Validation:
The visible production filesystem is about 930 MiB, including 594 MiB of dependencies. Prisma CLI remains for startup migrations. No bot startup or database migrations were performed.