Now go forth and configure safely.
Remember: commit the shared .env.development , ignore the local .env.development.local , and always respect the load order. Do this, and you will never again have the dreaded "but it works on my machine" argument over environment variables. .env.development.local
.env.local .env.*.local This ensures that no machine-specific file ever reaches your repository. Because .env.development.local is not committed, new developers won't have it. Create a .env.example or a README.md that lists what keys a developer should place in their local file. Now go forth and configure safely
Suppose you have three files in your project root: ignore the local .env.development.local
Many developers have committed their .env.development.local to Git by mistake. Once that happens, even if you delete it, the secret remains in the Git history forever.