feat: [INFRA] Harden Dockerfile for production - #771
Merged
jahrulezfrancis merged 3 commits intoAug 30, 2026
Conversation
|
@SYLVIANNORUKA is attempting to deploy a commit to the indexhtml's projects Team on Vercel. A member of the Team first needs to authorize it. |
Collaborator
|
@SYLVIANNORUKA Kindly provide a more detailed PR description for your implementation, it helps with backlog! |
jahrulezfrancis
approved these changes
Aug 30, 2026
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
|
@SYLVIANNORUKA Thanks for your contributions. LGTM!!! |
Closed
4 tasks
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
2 participants
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.
[INFRA] Harden Dockerfile for production (multi-stage, non-root, native deps, healthcheck)
closes #739
[INFRA] Harden Dockerfile for production
tags:
infradockerproductionSummary
Hardens the Dockerfile for production: multi-stage build, non-root runtime user, isolated native-dependency compilation, and a container-level healthcheck.
Motivation
The current image ships the full build toolchain, dev dependencies, and runs as root — bigger attack surface than needed, larger image size, and no way for the orchestrator to know if the app is actually healthy vs. just "the process is up."
Changes
1. Multi-stage build
Three stages:
deps(installs all deps + native build toolchain) →build(compiles, thennpm prune --omit=dev) →runtime(onlynode_modules,