fix: use POSTGRES_PRISMA_URL for integration

Author: Zac-Zajdel

.env.example

@@ -6,15 +6,15 @@ NEXT_PUBLIC_APP_URL=http://localhost:3000
 # -----------------------------------------------------------------------------
 # Local Database
 # -----------------------------------------------------------------------------
-DATABASE_URL=
+POSTGRES_PRISMA_URL=
 POSTGRES_URL_NON_POOLING=
 
 # -----------------------------------------------------------------------------
 # Database (Supabase)
-# DATABASE_URL: Connect to Supabase via connection pooling with Supavisor.
+# POSTGRES_PRISMA_URL: Connect to Supabase via connection pooling with Supavisor.
 # POSTGRES_URL_NON_POOLING: Direct connection to the database. Used for migrations.
 # -----------------------------------------------------------------------------
-DATABASE_URL=
+POSTGRES_PRISMA_URL=
 POSTGRES_URL_NON_POOLING=
 
 # -----------------------------------------------------------------------------

env.ts

@@ -3,7 +3,7 @@ import { z } from 'zod';
 
 export const env = createEnv({
   server: {
-    DATABASE_URL: z.string().url(),
+    POSTGRES_PRISMA_URL: z.string().url(),
     AUTH_SECRET: z.string().min(1),
     AUTH_GOOGLE_ID: z.string().min(1),
     AUTH_GOOGLE_SECRET: z.string().min(1),
@@ -13,7 +13,7 @@ export const env = createEnv({
   },
   runtimeEnv: {
     NEXT_PUBLIC_APP_URL: process.env.NEXT_PUBLIC_APP_URL,
-    DATABASE_URL: process.env.DATABASE_URL,
+    POSTGRES_PRISMA_URL: process.env.POSTGRES_PRISMA_URL,
     AUTH_SECRET: process.env.AUTH_SECRET,
     AUTH_GOOGLE_ID: process.env.AUTH_GOOGLE_ID,
     AUTH_GOOGLE_SECRET: process.env.AUTH_GOOGLE_SECRET,

prisma/schema.prisma

@@ -10,7 +10,7 @@ generator client {
 
 datasource db {
   provider = "postgresql"
-  url      = env("DATABASE_URL")
+  url      = env("POSTGRES_PRISMA_URL")
 }
 
 model Account {