-
Notifications
You must be signed in to change notification settings - Fork 3
docs: add prisma to 3rd party integrations #952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+2.36 MB
mintlify/content/docs/integrations/prisma/ppg-project-connection.webp
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| --- | ||
| title: Prisma | ||
| --- | ||
|
|
||
| [Prisma Postgres](https://www.prisma.io/postgres) is a fully managed serverless PostgreSQL that focuses on performance, with built-in connection pooling. | ||
|
|
||
| You can create a Prisma Postgres instance and use Bytebase to manage the database development lifecycle for those databases. | ||
|
|
||
| While Prisma Postgres already has developer-oriented features like branching, Bytebase adds extra value to offer a systematic database development and change workflow. This is especially useful for cross-functional teams requiring collaboration (e.g. having dedicated DBA or platform engineering team apart from the application development teams). | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| - [Sign up](https://console.prisma.io/) for Prisma Postgres, you can sign in with a Github Google account, or email and password. | ||
| - After signing in, you are directed to the Prisma Console where you can [set up your project](https://www.prisma.io/docs/postgres/). | ||
|
|
||
| ## Procedure | ||
|
|
||
| ### Step 1 - Set up project on Prisma Postgres and collect connection info | ||
|
|
||
| Once you have set up your project, click "Connect" button in the Connect Database card and copy the connection string that is generated for you. | ||
|
|
||
|
|
||
|  | ||
|
|
||
| With this connection string, we have the following information represented | ||
|
|
||
| ``` | ||
| postgresql://[username]:[password]@[host][:port]/[dbname][?param1=value1¶m2=value2] | ||
| ``` | ||
|
|
||
| ### Step 2 - Add Prisma Postgres instance to Bytebase | ||
|
|
||
| From your Bytebase **Create Instance** page, choose **Add Instance**, fill in the details to create the connection as follows: | ||
|
|
||
| 1. **Database:** `PostgreSQL`. | ||
| 2. **Instance Name:** any name of your choosing, e.g. `ppg-bb`. | ||
| 3. **Environment:** `Prod` or `Test` (select the environment you want to add the instance to). | ||
| 4. **Host or Socket:** the **host** section of the connection string: `db.prisma.io` | ||
| 5. **Port:** 5432 (Prisma Postgres uses the default PostgreSQL port of 5432 to connect) | ||
| 6. **Username:** copy the **username** section of the connection string | ||
| 7. **Password:** copy the **password** section of the connection string | ||
| 8. **Database:** copy the **dbname** section of the connection string: `postgres` | ||
|
|
||
|  | ||
|
|
||
| See [Add an Instance](/get-started/step-by-step/add-an-instance) for more details. | ||
|
|
||
| ### Step 3 - Check if the database instance is properly imported | ||
|
|
||
| All databases should be synced properly. Expect some delay if the database instance is large. | ||
|
|
||
| So should the tables under the databases. | ||
|
|
||
|  |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -91,4 +91,4 @@ | |
| "typescript": "^5.6.3", | ||
| "url-loader": "^4.1.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.
Uh oh!
There was an error while loading. Please reload this page.