.env.example

# README.md's section "Setting the environment variables" will help with this
DATABASE_URL="postgresql://databaseusername:databasepassword@localhost:5432/mydb?schema=public"

# the id of your spreadsheet. ID can be found inside the link after /d/ mark.
#For example https://docs.google.com/spreadsheets/d/1jlILhCXWB9wS2A3DMYZ2ZARGWlUBss4-u1JneTM0Owg/ -> 1jlILhCXWB9wS2A3DMYZ2ZARGWlUBss4-u1JneTM0Owg
SPREADSHEET_ID="1jlILhCXWB9wS2A3DMYZ2ZARGWlUBss4-u1JneTM0Owg"

# path of your Service Account's JSON file.
# for example if it was inside **utils** folder you should add it like this:
# "utils/google_service_account-steady-scope-436117-p2-f407b01106c9.json"
GOOGLE_SERVICE_ACCOUNT_JSON_FILE="google_service_account-arctic-diode-438812-b5-7338724a2dea.json"


# This variable is mostly used for deployable apps such as Vercel, Heroku app, etc
# Note: Vercel env variables cannot contain newlines, so you need to remove them from the JSON object
# Note: Vercel expects bare string without quotes around the string
# If GOOGLE_SERVICE_ACCOUNT_JSON_FILE and GOOGLE_SERVICE_ACCOUNT_CREDENTIALS are defined, GOOGLE_SERVICE_ACCOUNT_CREDENTIALS will take the priority
# Add into this variable the whole object inside Service Account's JSON file.
# Should look something like this:
GOOGLE_SERVICE_ACCOUNT_CREDENTIALS=`{
  "type": "service_account",
  "project_id": "your-project-id",
  "private_key_id": "your-private-key-id",
  "private_key": "your-private-key",
  "client_email": "your-client-email",
  "client_id": "your-client-id",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://accounts.google.com/o/oauth2/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "your-cert-url"
}`

# This is used in Vercel to secure the Cron Job API endpoint
# Vercel recommends to have a password with at least 16 characters
# More details: https://vercel.com/docs/cron-jobs/manage-cron-jobs#securing-cron-jobs
CRON_SECRET="secretPasswordHere"