-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
31 lines (21 loc) · 1 KB
/
Copy path.env.example
File metadata and controls
31 lines (21 loc) · 1 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
# Since .env is gitignored, you can use .env.example to build a new `.env` file when you clone the repo.
# Keep this file up-to-date when you add new variables to \`.env\`.
# This file will be committed to version control, so make sure not to have any secrets in it.
# If you are cloning this repo, create a copy of this file named `.env` and populate it with your secrets.
# The database URL is used to connect to your Supabase database.
POSTGRES_URL="postgres://postgres.[USERNAME]:[PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:6543/postgres?workaround=supabase-pooler.vercel"
# You can generate the secret via 'openssl rand -base64 32' on Unix
# @see https://www.better-auth.com/docs/installation
AUTH_SECRET='supersecret'
# Cache
REDIS_CONNECTION_STRING=''
# APP
NEXT_PUBLIC_BASE_URL=''
# Email
RESEND_FROM=''
RESEND_TOKEN=''
# Google auth secret
GOOGLE_CLIENT_ID=""
GOOGLE_CLIENT_SECRET=""
# Comma-separated emails granted the super_admin role on signup / via `pnpm -F @nucleus/db seed`
SUPER_ADMIN_EMAILS=""