Add instructions for building Next.js client with SSG locally in Docker Compose #1918
Conversation
This file contains 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
added 2 commits
March 14, 2024 10:10
…ient locally with SSG Added detailed instructions for building a Next.js client with Static Site Generation (SSG) in a Docker Compose environment. The steps include adjustments to the compose.prod.yaml file, starting the php service container, optional creation of a .env file for the Next.js client, building the pwa service, and finally bringing up the full project. This setup ensures the Next.js client can access the API at build time for static page generation.
…with docker compose Updated the Next.js documentation to include instructions for generating a production build locally using Docker Compose. The update provides a link to the detailed steps in the Docker Compose deployment guide.
J3m5
force-pushed
the
docker-nextjs-local-production-build
branch
from
8aee607
to
37fb0ec
Compare
… Kubernetes doc Added optional Docker build command for SSG projects in Kubernetes doc. This command allows the PWA to access a locally running API during the build process, useful for generating static pages at build time.
J3m5
force-pushed
the
docker-nextjs-local-production-build
branch
from
37fb0ec
to
400ed22
Compare
…variables To ensure TRUSTED_HOSTS and MERCURE_PUBLIC_URL remain valid when altering SERVER_NAME to use an HTTP scheme or include a port, these variables must be overridden. This adjustment accommodates configurations where SERVER_NAME deviates from the standard HTTPS format or includes port specifications.
|
@dunglas I have updated this pull request to reflect the changes made to the api-platform template in my previous PR. |
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.
This pull request adds detailed instructions for building a Next.js client with Static Site Generation (SSG) locally with http in a Docker Compose environment.
The steps include adjustments to the compose.yaml and compose.prod.yaml files, building and starting the php service container, optional creation of a .env file for the Next.js client, building the pwa service, and finally bringing up the full project.
This setup ensures the Next.js client can access the API locally at build time for static page generation.
The last commit adapt the docker compose documentation to reflect the changes of this PR adding the MERCURE_PUBLIC_URL and
TRUSTED_HOSTS environment variables.