Fix PostgreSQL SSL configuration in nextjs-postgres sample #420
+9
−1
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.
The nextjs-postgres sample was failing to deploy due to a PostgreSQL SSL configuration mismatch. The deployment logs showed:
Root Cause
The production
compose.yaml
hadPOSTGRES_SSL: true
but the standardpostgres:16
Docker image doesn't have SSL configured by default, causing the connection to fail.Changes Made
POSTGRES_SSL
fromtrue
tofalse
incompose.yaml
to match the reality that the PostgreSQL container doesn't support SSL connectionsTesting
POSTGRES_SSL: ""
)The fix is minimal and surgical - only one line changed in the core configuration file, with additional documentation for clarity. This aligns the configuration with the actual capabilities of the PostgreSQL Docker container being used.
Fixes #419.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.
Samples Checklist
✅ All good!