feat: Add Dockerfile for multi-stage build and production setup #471
+38
−0
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.
Add a multi-stage Dockerfile for building and running the inspector project in production.
Related: #466 (it is not closing, missing deployment pipeline)
Motivation and Context
This change enables building and running the project in a production-ready Docker container, reducing image size and ensuring only production dependencies are included. It also standardizes the deployment process.
How Has This Been Tested?
The Dockerfile was used to build and run the application locally. The build completed successfully, and the application started as expected in the container.
Breaking Changes
No breaking changes.
Types of changes
Checklist
Additional context
The Dockerfile uses a builder stage to install dependencies and build all packages, then a runner stage to install only production dependencies and copy the built artifacts. Ports 6274 and 6277 are exposed for service use. Uses
npm start
as the default command.