Add production Docker image - #247
Open
amicus-merakisys wants to merge 1 commit into
Open
Conversation
|
|
amicus-merakisys
force-pushed
the
add-production-dockerfile
branch
from
June 19, 2026 15:27
572a025 to
75a7daa
Compare
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
.dockerignoreto keep the Docker context cleanWhy this matters
The previous Dockerfile was optimized for local development: it installed dependencies, copied the source tree, and ran the React development server. That works for contributor workflows, but it is heavier and less predictable for deployment. A production image should compile once, ship only the generated static assets, and serve them from a small web server.
Making the main Dockerfile production-ready means the default Docker path now matches how this viewer should be deployed: smaller runtime surface, faster startup, static asset caching, and proper SPA fallback behavior.
Testing
NODE_OPTIONS=--openssl-legacy-provider npm run builddocker buildin this environment because Docker daemon access is unavailable: permission denied connecting to/var/run/docker.sock