/
.env.example
39 lines (29 loc) · 1.28 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
38
# 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.
# Vercel Postgres
POSTGRES_URL="************"
POSTGRES_PRISMA_URL="************"
POSTGRES_URL_NO_SSL="************"
POSTGRES_URL_NON_POOLING="************"
POSTGRES_USER="************"
POSTGRES_HOST="************"
POSTGRES_PASSWORD="************"
POSTGRES_DATABASE="************"
NEXT_PUBLIC_URL="http://localhost:3000"
# Uploadthing
UPLOADTHING_SECRET=""
UPLOADTHING_APP_ID=""
# optional global override for analytics
# can be used to diable analytics in development
#DISABLE_ANALYTICS=true
# optional manual specification for installation ID. Useful in scenarios such as
# CI/CD where the installation ID cannot be automatically determined because
# there is no database. Also useful for ensuring consistent ID between DB
# resets.
#INSTALLATION_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx