Bootstrap CodePress Live Dev Server recipe + dev Dockerfiles#9
Open
codepress-dev[bot] wants to merge 1 commit into
Open
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.
Generated by /codepress-bootstrap-dev-server. The recipe at
.codepress/dev-server/recipe.jsonplus the per-frontend dev Dockerfile drive the Live Dev Server.What this sets up
web(Create React App, react-scripts 1.0.10 / React 15)..codepress/dev-server/Dockerfile.webis a thin, dev-mode image that binds0.0.0.0, installsprocps, and runsyarn startwith HMR wired to the runtime env vars (PORT,CODEPRESS_BIND_HOST,CODEPRESS_HMR_CLIENT_PORT,CODEPRESS_HMR_PROTOCOL). It pins Node 18 with the legacy OpenSSL provider because this 2017-era CRA/webpack toolchain crashes on the OpenSSL 3 hashing error under current Node, and setsDANGEROUSLY_DISABLE_HOST_CHECK=trueso the preview proxy's Host header is accepted.Not changed (by design)
server/has no CORS allowlist and the React app makes no cross-origin API calls — Django serves the built SPA from its own static files (same-origin). There is no cross-origin CORS surface to configure, and the project has no staging-only settings path..env, CI, or config declares one, and the frontend reads no API base env var, so nothing was prefilled.Generated with CodePress