Skip to content

fix: make prisma provider configurable by env DATABASE_PROVIDER (#71)#72

Open
DavidutzDev wants to merge 7 commits into
ZimengXiong:mainfrom
DavidutzDev:prism-provider-config
Open

fix: make prisma provider configurable by env DATABASE_PROVIDER (#71)#72
DavidutzDev wants to merge 7 commits into
ZimengXiong:mainfrom
DavidutzDev:prism-provider-config

Conversation

@DavidutzDev
Copy link
Copy Markdown

This pull request is implementing the Prisma configurable provider by setting it to an env var.

Closing #71

@DavidutzDev DavidutzDev marked this pull request as draft February 24, 2026 21:57
@DavidutzDev DavidutzDev marked this pull request as ready for review February 24, 2026 21:59
@DavidutzDev DavidutzDev marked this pull request as draft February 24, 2026 22:19
…der switching

Allows container to use sqlite (default) or postgresql by setting
DATABASE_PROVIDER and DATABASE_URL environment variables at runtime.
@DavidutzDev DavidutzDev marked this pull request as ready for review February 24, 2026 22:42
…tabases provider and it's not really a good idea to do like this. This should only be a temporary fix
… stuff. Now we just create a separate migrations folder for postgres and update docker
@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented Feb 25, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic Password 5d3e19b docker-compose.pg-test.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@ZimengXiong ZimengXiong added enhancement New feature or request priority:p2 Important, but not urgent area:database Database and storage layer labels Apr 1, 2026
@ZimengXiong ZimengXiong self-requested a review April 2, 2026 22:06
@ZimengXiong ZimengXiong self-assigned this Apr 2, 2026
@biboc
Copy link
Copy Markdown

biboc commented Apr 3, 2026

Nice feature, that would allow to be very flexible and have remote DB
Thanks,

@ZimengXiong
Copy link
Copy Markdown
Owner

Copying over from #71

I do want to ask, how many of you are just interested in Postgres support, and don't care about other Prisma-supported db types, e.g. mysql, sqlserver, cockroachdb, and mongodb? I think it makes more sense to do a specific Postgres-scoped support instead of supporting all the different types of dbs in Prisma, I am guessing that is the most popular/only reason people are looking for multi-db support. This would make support going fwd easier and scope smaller.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:database Database and storage layer enhancement New feature or request priority:p2 Important, but not urgent

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants