Skip to content

Commit 2c20a86

Browse files
authored
Docs for v6.17.0 (#7133)
* no required login for local ppg workflows * remove preview label from direct connections page * update flow for getting direct connection string * add workspace metrics * add workspace metrics * add prisma config updates * revert changes to prisma config * remove note about no login for local ppg management in vs code * revise connection details * Apply suggestion from @nikolasburk * Apply suggestion from @nikolasburk
1 parent 7071f46 commit 2c20a86

File tree

4 files changed

+31
-18
lines changed

4 files changed

+31
-18
lines changed

content/200-orm/500-reference/325-prisma-config-reference.mdx

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,12 @@ Here is a simplified version of the `PrismaConfig` type:
5555

5656
```ts
5757
export declare type PrismaConfig = {
58+
5859
// Whether features with an unstable API are enabled.
5960
experimental: {
60-
adapter: true,
61-
externalTables: true,
62-
studio: true,
61+
adapter: boolean;
62+
externalTables: boolean;
63+
studio: boolean;
6364
},
6465

6566
// The path to the schema file, or path to a folder that shall be recursively searched for *.prisma files.
@@ -68,7 +69,7 @@ export declare type PrismaConfig = {
6869
// The Driver Adapter used for Prisma CLI.
6970
adapter?: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
7071

71-
// The configuration for Prisma Studio.
72+
// Configuration for Prisma Studio.
7273
studio?: {
7374
adapter: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
7475
};
@@ -89,6 +90,7 @@ export declare type PrismaConfig = {
8990
typedSql?: {
9091
path: string;
9192
};
93+
9294
};
9395
```
9496

@@ -486,4 +488,4 @@ You can specify a custom location for your config file when running Prisma CLI c
486488

487489
```terminal
488490
prisma validate --config ./path/to/myconfig.ts
489-
```
491+
```

content/250-postgres/100-introduction/200-getting-started.mdx

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -54,12 +54,11 @@ prisma generate --no-engine
5454
You can access Prisma Postgres with any ORM or database tool of your choice via [direct TCP connections](/postgres/database/direct-connections).
5555

5656
In order to get a direct TCP connection string, you need to:
57-
1. open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
58-
1. navigate to a environment with an active Prisma Postgres instance
59-
1. click the **API Keys** tab in the project's sidenav
60-
1. click the **Create API key** button
61-
1. in the popup, provide a **Name** for the API key and click **Create**
62-
1. copy the connection string starting with `postgres://`, this is your direct TCP connection string
57+
1. Navigate to your active Prisma Postgres instance.
58+
1. Click the **API Keys** tab in the project's sidenav.
59+
1. Click the **Create API key** button.
60+
1. In the popup, provide a **Name** for the API key and click **Create**.
61+
1. Copy the connection string starting with `postgres://`, this is your direct connection string.
6362

6463
Once you have the connection string, you can follow the setup docs for PostgreSQL of any ORM or database tool:
6564

content/250-postgres/100-introduction/250-overview.mdx

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,21 @@ toc: true
1111

1212
It supports the following workflows:
1313

14-
- Schema migrations and queries (via [Prisma ORM](https://www.prisma.io/orm))
14+
- Schema migrations and queries (via [Prisma ORM](https://www.prisma.io/orm) or any other ORM/database library)
1515
- Connection pooling and caching (via [Prisma Accelerate](https://www.prisma.io/accelerate))
16+
- Local database workflows via [`prisma dev`](/postgres/database/local-development)
17+
18+
## Usage metrics
19+
20+
You can view the following usage metrics in your Console Dashboard:
21+
22+
- Key metrics
23+
- Estimated upcoming invoice
24+
- Total storage used
25+
- Total DBs
26+
- Overall usage
27+
- Cumulative operations
28+
- Operations per day
1629

1730
## Billing
1831

content/250-postgres/300-database/650-direct-connections.mdx

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@ metaTitle: "Direct connections (TCP)"
44
metaDescription: "Learn about connecting directly to your Prisma Postgres database via direct TCP."
55
tocDepth: 3
66
toc: true
7-
sidebar_class_name: preview-badge
87
---
98

109
## Overview
@@ -18,11 +17,11 @@ If you connect to it via another tool, you can do so with a [direct connection s
1817
In order to get a direct connection string, you need to:
1918

2019
1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
21-
1. Navigate to a environment with an active Prisma Postgres instance
22-
1. Click the **API Keys** tab in the project's sidenav
23-
1. Click the **Create API key** button
24-
1. In the popup, provide a **Name** for the API key and click **Create**
25-
1. Copy the connection string starting with `postgres://`, this is your direct connection string
20+
1. Navigate to your active Prisma Postgres instance.
21+
1. Click the **API Keys** tab in the project's sidenav.
22+
1. Click the **Create API key** button.
23+
1. In the popup, provide a **Name** for the API key and click **Create**.
24+
1. Copy the connection string starting with `postgres://`, this is your direct connection string.
2625

2726
## Connection string
2827

0 commit comments

Comments
 (0)