-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy path.env.example
37 lines (29 loc) · 1.5 KB
/
.env.example
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
31
32
33
34
35
36
37
# Since the ".env" file is gitignored, you can use the ".env.example" file 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.
# When adding additional environment variables, the schema in "/src/env.js"
# should be updated accordingly.
# Prisma
# https://www.prisma.io/docs/reference/database-reference/connection-urls#env
DATABASE_URL="postgresql://postgres:mysecretpassword@localhost:5432/postgres"
# Next Auth
# You can generate a new secret on the command line with:
# openssl rand -base64 32
# https://next-auth.js.org/configuration/options#secret
AUTH_SECRET=""
AUTH_URL="http://localhost:3000"
# Next Auth Google Provider
#
# https://next-auth.js.org/providers/google
#
# I suggest this tutorial for the google setup portion https://refine.dev/blog/nextauth-google-github-authentication-nextjs/#for-googleprovider-make-sure-you-have-a-google-account
AUTH_GOOGLE_ID="Something somthing"
AUTH_GOOGLE_SECRET="something somthing"
# Stripe
STRIPE_SECRET_KEY="Configure this in the stripe dashboard"
# STRIPE_WEBHOOK_SECRET="output of `stripe listen --print-secret`, it is added to env during `npm run dev`, no need to add it here"
STRIPE_PRODUCT_ID_PLUS="Configure this in the stripe dashboard"
STRIPE_PRODUCT_ID_PRO="Configure this in the stripe dashboard"