.env-example

# 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.

# When adding additional env variables, the schema in /env/schema.mjs should be updated accordingly

# Prisma
DATABASE_URL=postgres://USER:PASSWORD@HOST:PORT/DATABASE

# Next Auth
NEXTAUTH_SECRET=
NEXTAUTH_URL=http://localhost:3000

# Next Auth Google Provider
GOOGLE_CLIENT_ID=
GOOGLE_CLIENT_SECRET=

# AWS
# These names look like this, because you cannot set `AWS_ACCESS_KEY_ID` as an env variable on Vercel
AMAZON_WS_ACCESS_KEY_ID=
AMAZON_WS_SECRET_ACCESS_KEY=
AMAZON_WS_REGION=
AMAZON_WS_IDENTITY_POLL_ID=