feat: NEXT_PUBLIC_REQUIRE_EMAIL_VERIFICATION/EMAIL_FROM

[chollinger93]

What

I tried self hosting this (seems like a cool project, thank you) but couldn't get past the demo screen, since email validation is required, but the sender email is also hard-coded.

This lets you configure both as:

EMAIL_FROM=example@example.org
NEXT_PUBLIC_REQUIRE_EMAIL_VERIFICATION=false

How

Followed the pattern of adding the environment variables as constant where they're used. I'd suggest centralizing the data model.

Test

docker run  \
  -p 3001:3000 \
  -e DS_SECRET_KEY="$(openssl rand -base64 32 | tr -d '\n')" \
  -e BETTER_AUTH_SECRET="$(openssl rand -hex 32)" \
  -e BETTER_AUTH_URL="http://localhost:3000" \
  -e DORY_AI_PROVIDER=openai \
  -e DORY_AI_MODEL=gpt-4o-mini \
  -e DORY_AI_API_KEY=your_api_key_here \
  -e DORY_AI_URL=https://api.openai.com/v1 \
  -e NEXT_PUBLIC_REQUIRE_EMAIL_VERIFICATION=false \
  $(docker build -q .)

[vercel]

@chollinger93 is attempting to deploy a commit to the DoryFinn's projects Team on Vercel.

A member of the Team first needs to authorize it.