Never do in ENV files what can be done in config files

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job. You're in the collaboration category.

Last Updated: 2021-05-15

During the start of the Project S project, I modified the env file perhaps once every day.

Because the env file exists outside of git, it must be laboriously sent to other developers. And sometimes they don't bother updating it, leading to huge misunderstandings and slow-down when they can't get the code running.


Never do in env files what can be done in config files. It's worth taking the extra half an hour to learn how to do this in your given framework (if you don't already know).