1) Can someone confirm that the instructions here https://docs.nhost.io/platform/environment-variables to redeploy are required: "When an Environment Variable is changed, you must deploy your project again using the GitHub integration for the changes to take effect." If needed, is there a "redeploy" option/button without making an unneeded code change via GH? Yesterday I felt like it was _not_ needed - I'd change an ENV value and a few minutes later I think I'd see in the logs a NHost servers restart. But it's actually quite difficult to tell - there's not actually a line that says 'Restarting' nor one that says 'Server up'. Just now I made a change and the change definitely did NOT take as far as I can tell - I added my own logging in a Function of the ENV values at startup. And opening and saving the Dashboard's > Settings > Env value didn't cause the same type of restart. Suggestions needed! 2) I'm curious about the `.env.development` file. First, does `.env.development` have any effect on the live project if it's included in the GH repo? I believe it _doesn't_ but looking for confirmation. Second, isn't it generally the case that the .env files should _not_ be added to git? Esp if they contain secrets - and typically people do add them here. Yes, it's local secrets but that shouldn't be assumed. So I'm wondering whether the code here should include `.env.development` in `.gitignore` by default since CLI writes the initial file. https://github.com/nhost/cli/blob/a23f8ceebf2d87f932559d4bce0570fe59da68d3/cmd/init.go#L223