Skip to content

feat: Add Dockerfile for multi-stage build and production setup #471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

baruchiro
Copy link

@baruchiro baruchiro commented May 30, 2025

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

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.

@cliffhall cliffhall added the duplicate This issue or pull request already exists label Jun 2, 2025
@cliffhall
Copy link
Contributor

Marking as a duplicate of #257

@cliffhall cliffhall mentioned this pull request Jun 2, 2025
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants