docs(): update migration getting started

Author: mhartington

content/200-orm/300-prisma-migrate/050-getting-started.mdx

@@ -14,83 +14,129 @@ To get started with Prisma Migrate in a development environment:
 
 1.  Create a Prisma schema:
 
-    ```prisma file=schema.prisma showLineNumbers
-    datasource db {
-      provider = "postgresql"
-    }
-    
-    model User {
-      id    Int    @id @default(autoincrement())
-      name  String
-      posts Post[]
-    }
-    
-    model Post {
-      id        Int     @id @default(autoincrement())
-      title     String
-      published Boolean @default(true)
-      authorId  Int
-      author    User    @relation(fields: [authorId], references: [id])
-    }
-    ```
+<TabbedContent code groupId="schema">
+<TabItem value="Prisma 7">
+
+```prisma file=schema.prisma showLineNumbers
+datasource db {
+  provider = "postgresql"
+}
+
+model User {
+  id    Int    @id @default(autoincrement())
+  name  String
+  posts Post[]
+}
 
-    :::tip
+model Post {
+  id        Int     @id @default(autoincrement())
+  title     String
+  published Boolean @default(true)
+  authorId  Int
+  author    User    @relation(fields: [authorId], references: [id])
+}
+```
 
-    You can use [native type mapping attributes](/orm/prisma-migrate/workflows/native-database-types) in your schema to decide which exact database type to create (for example, `String` can map to `varchar(100)` or `text`).
 
-    :::
+</TabItem>
 
-    
+<TabItem value="Prisma 6">
 
-    1.  Create the first migration:
+```prisma file=schema.prisma showLineNumbers
+datasource db {
+  provider = "postgresql"
+  url      = env("DATABASE_URL")
+}
 
-    <CodeWithResult showText="Show migration SQL" hideText="Hide migration SQL">
+model User {
+  id    Int    @id @default(autoincrement())
+  name  String
+  posts Post[]
+}
 
-    <cmd>
+model Post {
+  id        Int     @id @default(autoincrement())
+  title     String
+  published Boolean @default(true)
+  authorId  Int
+  author    User    @relation(fields: [authorId], references: [id])
+}
+```
 
-    ```terminal
-    prisma migrate dev --name init
-    ```
+</TabItem>
+</TabbedContent>
 
-    </cmd>
+:::tip
 
-    <cmdResult>
+You can use [native type mapping attributes](/orm/prisma-migrate/workflows/native-database-types) in your schema to decide which exact database type to create (for example, `String` can map to `varchar(100)` or `text`).
 
-    ```sql no-copy
-      -- CreateTable
-    CREATE TABLE "User" (
-        "id" SERIAL,
-        "name" TEXT NOT NULL,
-
-        PRIMARY KEY ("id")
-    );
-      -- CreateTable
-    CREATE TABLE "Post" (
-        "id" SERIAL,
-        "title" TEXT NOT NULL,
-        "published" BOOLEAN NOT NULL DEFAULT true,
-        "authorId" INTEGER NOT NULL,
-
-        PRIMARY KEY ("id")
-    );
-
-      -- AddForeignKey
-    ALTER TABLE "Post" ADD FOREIGN KEY("authorId")REFERENCES "User"("id") ON DELETE CASCADE ON UPDATE CASCADE;
-    ```
+:::
 
-    </cmdResult>
+For Prisma 7, be sure to have a `prisma.config.ts` in the root of your project:
 
-    > **Note**: If you do not provide a `--name`, Prisma CLI will prompt you for a name.
+```ts file=prisma.config.ts showLineNumbers
+import 'dotenv/config'
+import { defineConfig, env } from "prisma/config";
+export default defineConfig({
+  schema: "prisma/schema.prisma",
+  migrations: {
+    path: "prisma/migrations",
+  },
+  datasource: {
+    url: env("DATABASE_URL"),
+  },
+});
+```
 
-    </CodeWithResult>
+  1.  Create the first migration:
 
-    Your Prisma schema is now in sync with your database schema and you have initialized a migration history:
+  <CodeWithResult showText="Show migration SQL" hideText="Hide migration SQL">
 
-    ```
-    migrations/
-      └─ 20210313140442_init/
-        └─ migration.sql
-    ```
+  <cmd>
+
+  ```terminal
+  prisma migrate dev --name init
+  ```
+
+  </cmd>
+
+  <cmdResult>
+
+  ```sql no-copy
+    -- CreateTable
+  CREATE TABLE "User" (
+      "id" SERIAL,
+      "name" TEXT NOT NULL,
+
+      PRIMARY KEY ("id")
+  );
+    -- CreateTable
+  CREATE TABLE "Post" (
+      "id" SERIAL,
+      "title" TEXT NOT NULL,
+      "published" BOOLEAN NOT NULL DEFAULT true,
+      "authorId" INTEGER NOT NULL,
+
+      PRIMARY KEY ("id")
+  );
+
+    -- AddForeignKey
+  ALTER TABLE "Post" ADD FOREIGN KEY("authorId")REFERENCES "User"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+  ```
+
+  </cmdResult>
+
+  > **Note**: If you do not provide a `--name`, Prisma CLI will prompt you for a name.
+
+  </CodeWithResult>
+
+  Your Prisma schema is now in sync with your database schema and you have initialized a migration history:
+
+  ```
+  migrations/
+    └─ 20210313140442_init/
+      └─ migration.sql
+  ```
 
 1.  Add additional fields to your schema: