next-auth: better env.example about create-t3-app HOT 6 CLOSED

NEXTAUTH_URL is only for production (right?) so no need to include it in a dev .env-example.

from create-t3-app.

It's the secret that will sort of work in dev but will not in prod (they auto-generate a secret for dev).
The URL should be set always, but for things like Vercel previews and Vercel deployments, it will use VERCEL_URL.
https://next-auth.js.org/warnings#nextauth_url
https://next-auth.js.org/warnings#no_secret
https://next-auth.js.org/configuration/options#secret
The last one lists all the reasons why should not depend on the auto secret generation and that it will be removed, and it boggles my mind why they would ever come up with something like that in the first place.

from create-t3-app.

Oh right. You dont need it with Vercel was probably what I was thinking about.

Add 2 rows to the .env-example then. I dont think we need to parametrize it or autogenerate a secret to use. The file is an example and it is up to the user to set their own secrets.

from create-t3-app.

Oh right. You dont need it with Vercel was probably what I was thinking about.

Add 2 rows to the .env-example then. I dont think we need to parametrize it or autogenerate a secret to use. The file is an example and it is up to the user to set their own secrets.

from create-t3-app.

I totally agree that generating a secret goes too far beyond scaffolding so it's not a concern of this app.

from create-t3-app.

Implemented in #114

from create-t3-app.