A .env file is a simple configuration file used to define . Instead of hardcoding sensitive information (like API keys) or environment-specific settings (like database URLs) directly into your source code, you store them in this file as key-value pairs. Example of a .env file:
Prefix your variables (e.g., MYAPP_PORT instead of just PORT ) to avoid clashing with system-level variables. Do not use spaces around the equals sign (e
Do not use spaces around the equals sign (e.g., KEY = VALUE will often fail; use KEY=VALUE ). You can pass a
PORT=3000 DATABASE_URL=postgres://user:password@localhost:5432/mydb STRIPE_API_KEY=sk_test_4eC39HqLyjWDarjtT1zdp7dc DEBUG=true Use code with caution. Why Use .env Instead of Hardcoding? KEY = VALUE will often fail
You can pass a .env file directly using the --env-file flag. Common Pitfalls to Avoid
You never want your private credentials (AWS keys, database passwords) to live in your version control system (like GitHub). By using a .env file, you can keep secrets local to your machine.