You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running ./start-database.sh generates an .env-e file, which is not gitignored and which contains AUTH_SECRET with the same value as the generated .env file
maieutiquer
changed the title
bug: non-ignored .env-e file created with exposed AUTH_SECRET
bug: start-database.sh creates non-ignored .env-e file with exposed AUTH_SECRET
Feb 22, 2025
maieutiquer
changed the title
bug: start-database.sh creates non-ignored .env-e file with exposed AUTH_SECRET
bug: start-database.sh creates non-ignored .env-e file with exposed AUTH_SECRET on macOS
Feb 22, 2025
maieutiquer
added a commit
to maieutiquer/create-t3-app
that referenced
this issue
Feb 22, 2025
Provide environment information
Describe the bug
Running
./start-database.sh
generates an.env-e
file, which is not gitignored and which contains AUTH_SECRET with the same value as the generated .env fileReproduction repo
https://github.com/t3-oss/create-t3-app
To reproduce
npm create t3-app@latest
and selected Yes to everything, NextAuth.js, Prisma and PostgreSQL../start-database.sh
Additional information
Potential solution
I tested that removing the
-e
from thesed
command and replacing it with''
prevents this file from being created.The text was updated successfully, but these errors were encountered: