fix: make prisma provider configurable by env DATABASE_PROVIDER (#71)#72
fix: make prisma provider configurable by env DATABASE_PROVIDER (#71)#72DavidutzDev wants to merge 7 commits into
Conversation
…der switching Allows container to use sqlite (default) or postgresql by setting DATABASE_PROVIDER and DATABASE_URL environment variables at runtime.
…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 id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | Generic Password | 5d3e19b | docker-compose.pg-test.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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.
fix: health check, because kubernetes do it in http
|
Nice feature, that would allow to be very flexible and have remote DB |
|
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. |
This pull request is implementing the Prisma configurable provider by setting it to an env var.
Closing #71