Skip to content

Conversation

aidankmcalister
Copy link

@aidankmcalister aidankmcalister commented Aug 1, 2025

🔎 Previews:

What does this solve?

  • Missing Documentation: There was no existing guide for integrating Clerk with Prisma Postgres
  • Developer Need: Developers using Prisma Postgres needed a clear tutorial on how to integrate with Clerk authentication
  • Complete Integration: Provides a full example of Clerk + Prisma Postgres + Prisma ORM setup from scratch

What changed?

  • New File: Created docs/integrations/databases/prisma-postgres.mdx as a complete new guide
  • Simple Schema: Uses a basic UserMessage model to demonstrate Clerk + Prisma integration
  • Server Actions: Shows how to use Clerk's auth() helper with Prisma for database operations
  • Complete Tutorial: Includes project setup, middleware configuration, schema definition, and UI implementation
  • Clear Structure: Follows a logical flow from setup to running the application

Checklist

  • I have clicked on "Files changed" and performed a thorough self-review
  • All existing checks pass

@aidankmcalister aidankmcalister requested a review from a team as a code owner August 1, 2025 15:46
Copy link

vercel bot commented Aug 1, 2025

@aidankmcalister is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

vercel bot commented Sep 16, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
clerk-docs Ready Ready Preview Sep 16, 2025 8:25pm

@NWylynko
Copy link
Contributor

Thank you Aidan for writing this guide, I'll run through it now! I've added a preview link if you'd like to see how it looks on the docs site.

@alexisintech
Copy link
Member

I'll have a final review here once Aidan addresses Nick's comments :)

@aidankmcalister
Copy link
Author

aidankmcalister commented Sep 16, 2025

Thank you for taking a look at this!

@alexisintech, I've implemented the changes requested by @NWylynko and made additional updates to align with the latest version of Prisma ORM (v6.16).

One of the changes I made was:

  generator client {
    // Change the provider from "prisma-client-js" to "prisma-client"
    provider = "prisma-client"
    output   = "../app/generated/prisma"
  }

I'm not sure about the proper title for it, but is there a flag that can indicate to remove this line and add this one? Similar to how other docs and GitHub use red for removal and green for addition.

@alexisintech
Copy link
Member

Thank you for taking a look at this!

@alexisintech, I've implemented the changes requested by @NWylynko and made additional updates to align with the latest version of Prisma ORM (v6.16).

One of the changes I made was:

  generator client {
    // Change the provider from "prisma-client-js" to "prisma-client"
    provider = "prisma-client"
    output   = "../app/generated/prisma"
  }

I'm not sure about the proper title for it, but is there a flag that can indicate to remove this line and add this one? Similar to how other docs and GitHub use red for removal and green for addition.

yes! see this section in our contributing guide: https://github.com/clerk/clerk-docs/blob/main/CONTRIBUTING.md#highlighting

you can write something like

+  the addition
-  the removal

using + and -

Comment on lines +19 to +25
## Create a new Next.js project

Create a new Next.js project using the following command:

```sh {{ filename: 'terminal' }}
npx create-next-app clerk-prisma-example --typescript --eslint --tailwind --use-npm --no-src-dir --app --import-alias "@/*"
```
Copy link
Member

@alexisintech alexisintech Sep 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we like to have users start from the nextjs quickstart, and then hit this guide. so this part shouldn't be necessary.

the guide should be written as if the user just came from the quickstart - the next step would be what do they need to install for the guide.

with this in mind, i think these first two sections ("create a new nextjs project" and "integrate the nextjs clerk sdk") need a bit of restructuring

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. I should be able do that tomorrow then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants