Why Can't We Commit .env Files?
Read full transcript 1 segments
-
Why can't we commit our environment Why can't we commit our environment files? It sounds stupid when I put it on files? It sounds stupid when I put it on files? It sounds stupid when I put it on a slide like this, but I want you to a slide like this, but I want you to a slide like this, but I want you to really think about this for a second. really think about this for a second. really think about this for a second. When I have a team of engineers that are When I have a team of engineers that are When I have a team of engineers that are working on a project, why do I have to working on a project, why do I have to working on a project, why do I have to build another system to share this build another system to share this build another system to share this specific file, but all the other files specific file, but all the other files specific file, but all the other files can go in Git just fine? We have to take can go in Git just fine? We have to take can go in Git just fine? We have to take a step back and think, is this how we do a step back and think, is this how we do a step back and think, is this how we do things cuz it's right, or is this how we things cuz it's right, or is this how we things cuz it's right, or is this how we do things cuz it's just how we've always do things cuz it's just how we've always do things cuz it's just how we've always done it?
Summary
The transcript questions why environment files, unlike other project files, are often excluded from Git, leading to the creation of separate sharing systems. It urges a reflection on whether this practice stems from necessity or simply inertia. The takeaway is to re-evaluate established workflows and consider integrating environment files into version control for better team collaboration.