Why .env file is ignored in production?

You say dotenv is only for development like it's a best practice, yet you store environment variables in a JSON file not excluded in .gitignore, against best practices... :upside_down_face:
That dotenv condition to only run in development doesn't make sense to people like me, JonL, tbvgl and similar. The only possible problem here is if somewhere along Wappler life you forgot to ignore .env files from being uploaded in deployments, so if you were to remove that condition and people had a .env file uploaded it could mess things up.

I'm not using Wappler targets because of the following issues or feature requests:
1. Lack of Docker image push deployment method
2. Lack of Git push deployment method
3. Slow SFTP deployment compared to rsync

You make it so difficult for me :sob:

1 Like