how to see changes on .env file when .env is in .gitignore
I'd still like to see the changes to my .env periodically and was wondering if anyone has any advice around this
2 Replies
never commit your env variables, but for the structure of your .env, the validation file create-t3-app provides should be good. If you're not using ct3a, creating an .env.example file with the keys is common. like
.env.example
I'm working on an open source project, which happens to be a monorepo that seemingly changed the way their env variables were organized, from a single matter dot env to one per package and app back to a single dot env file. The file also is heavily commented so I just wanted to see how to quickly find the diff between three current version and the version I have before the change.