استخدام dotenv في التطوير

Typing export for ten variables every session is tedious and easy to forget. A .env file fixes that for local work.

A .env file is plain text with KEY=value lines. It lives at your project root and feeds variables in automatically.

The python-dotenv package reads that file and loads each line into the environment for you.

Call load_dotenv early, before you read any config, so os.environ already holds the file values.

Recent Flask versions auto-load .env and .flaskenv when python-dotenv is installed, so flask run just works.

Put Flask-specific knobs like FLASK_APP in .flaskenv, and keep real secrets in .env instead.

Add .env to .gitignore so your local secrets never reach the repository by accident.

Commit a .env.example listing the needed keys with blank or dummy values, so teammates know what to set.

By default load_dotenv will not overwrite a variable already set in the real environment, which keeps prod safe.

Treat .env as a development convenience. In production, let the platform inject real environment variables instead.

A .env file supports # comments and quotes around values with spaces, just like a tiny config format.

Why must the .env file be added to .gitignore?

You stored local config in a .env file, loaded it with python-dotenv, gitignored it, and shared a safe example. 🧪