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

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

# Notion
NOTION_TOKEN=
NOTION_DATABASE_ID=

# Gooogle
GOOGLE_CLIENT_ID=
GOOGLE_CLIENT_SECRET=

# Nodemailer
EMAIL_SERVER=smtp://username:password@smtp.example.com:587
EMAIL_FROM=noreply@example.com

EMAIL_SERVER_HOST=
EMAIL_SERVER_PORT=
EMAIL_SERVER_USER=
EMAIL_SERVER_PASSWORD=

# Vercel
NEXT_PUBLIC_HOSTNAME=http://localhost:3000

# Figma
FIGMA_TOKEN=

# Env
NEXT_PUBLIC_NODE_ENV=development