Since the .env is not under version control, it often happens that developers are missing new values added by other developers. Also the .env.example is often totally out of date, cause the team forgot to add new values to it. Thats a pain, when a new developer joind the team and tries to setup the project. Often .env files get shared around, send via email or something like that. But this is not realy a generic and solid solution. Best would be, if the .env.example would just be up-to-date! Lets try to configure some githooks to ensure our .env and .env.example always stays up to date!