When you initialize a project, you should ensure your .gitignore file includes the following lines:
"files.associations": ".env.development.local": "env", ".env*.local": "env" .env.development.local
Beyond security, the file offers a level of granular control that shared files like .env.development cannot. Imagine a scenario where a team is building an app that interacts with a payment processor. Most developers might use a shared "test" account defined in .env.development . However, a lead developer working on a specific edge case might need to use a different test account. By defining those keys in .env.development.local , they can override the team-wide settings without changing a single line of shared code. Conclusion When you initialize a project, you should ensure your
# .env.production.local (Ignored) NODE_OPTIONS="--inspect" LOG_LEVEL="debug" However, a lead developer working on a specific
: Indicates that this file is machine-specific . It is intended to override other configurations just for your computer and should never be committed to version control. The Hierarchy: Who Wins?
# ----------------------------------------------------------- # General Settings # ----------------------------------------------------------- NODE_ENV=development APP_ENV=local
How this file behaves depends on your stack. Let's look at the heavy hitters.