-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
31 lines (24 loc) · 1.42 KB
/
.env.example
File metadata and controls
31 lines (24 loc) · 1.42 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
# Environment Variables (example)
# Copy this file to `.env` and replace the placeholders with your real values.
# IMPORTANT: Do NOT commit real secrets to the repository.
# Primary database connection (Postgres example)
# Format: postgresql://<user>:<password>@<host>:<port>/<db>?schema=public
DATABASE_URL="postgresql://username:password@localhost:5432/copo_db?sslmode=require"
# Shadow DB for Prisma Migrate (optional but recommended for dev)
# Example: a separate DB used for applying migrations safely
DATABASE_SHADOW_URL="postgresql://username:password@localhost:5433/copo_shadow_db?sslmode=require"
# NextAuth / session config (example)
NEXTAUTH_URL="http://localhost:3000"
NEXTAUTH_SECRET="your-super-secret-key-here"
# If using Prisma Accelerate (hosted), set this instead of a direct DB URL
# Example: PRISMA_ACCELERATE_URL="prisma+accelerate://<token>@<org>"
# When set, the Prisma client will prefer the Accelerate connection.
PRISMA_ACCELERATE_URL=""
# App runtime helpers
NEXT_PUBLIC_BASE_URL="http://localhost:3000"
NODE_ENV=development
PORT=3000
# Notes:
# - After setting `.env`, run `npx prisma generate` and `npx prisma migrate dev --name init` (or `npm run db:migrate`) to apply schema and generate the client.
# - For Prisma Accelerate workflows, consult https://pris.ly/d/prisma7-client-config and set PRISMA_ACCELERATE_URL appropriately.
# - Keep secrets in environment variables or a proper secrets manager in production.