/
.env.example
35 lines (29 loc) · 1.35 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
# 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.mjs" #
# should be updated accordingly. #
##################################################
NODE_ENV="development" # development | test | production
# Prisma
# https://www.prisma.io/docs/reference/database-reference/connection-urls#env
# Prisma
# https://www.prisma.io/docs/reference/database-reference/connection-urls#env
DATABASE_URL_PRISMA=''
DATABASE_URL_NODE=''
# 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
# Not providing any secret or NEXTAUTH_SECRET will throw an error in production.
# Leaving this empty in development won't throw an error, but may result in JWT decryption errors.
NEXTAUTH_SECRET=""
NEXTAUTH_URL="http://localhost:3000"
# Next Auth Github Provider
GITHUB_ID=""
GITHUB_SECRET=""