fix(db): support PostgreSQL environment variables at runtime - #923
Open
onmax wants to merge 1 commit into
Open
Conversation
|
@onmax is attempting to deploy a commit to the NuxtLabs Team on Vercel. A member of the Team first needs to authorize it. |
commit: |
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
1 participant
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.
NuxtHub's generated non-Cloudflare
postgres-jsclient currently rejects runtime configuration unless a connection URL is available. That prevents Postgres.js from applying its nativePG*environment fallback and forces container deployments to serialize discrete credentials into a URL.This keeps the existing URL priority unchanged. When no URL is available but
PGHOST,PGPORT,PGDATABASE,PGUSERNAME/PGUSER, orPGPASSWORDis set, the generated client now invokes Postgres.js with the configured options and lets the driver resolve its environment. With neither input form, the existing NuxtHub configuration error remains.The change is limited to the explicit non-Cloudflare production
postgres-jsruntime. Driver detection, build and development migrations, Cloudflare, Neon, and replica configuration are unchanged.