Environment Variables: export, env, printenv & .env Loading

In Plain English

Environment variables are globally accessible key-value pairs inherited by child processes. The `export` command promotes a local shell variable into the environment table. Loading `.env` files safely without executing arbitrary code is a staple of production deployment.

The Mental Model

"A regular variable is a note on your personal desk; an `export` variable is a company-wide memo broadcast to every worker and contractor in the building."

Deep Dive: How It Works

export Mechanism: Without `export`, variables remain private to the current shell process; `export VAR="val"` copies them to all child subprocesses.

Inspecting Environment: `printenv` or `env` lists all exported variables.

Safe `.env` Loading: `set -a; source .env; set +a` automatically exports all declared variables in the dotenv file.

Syntax Blueprint

export DATABASE_URL="postgres://user:pass@host:5432/db"
export PORT=8080

# Safe .env loader in scripts:
if [[ -f ".env" ]]; then
  set -a
  source .env
  set +a
fi

Use export for child inheritance and set -a to auto-export sourced .env keys.

Core Rules to Remember

Child Process Inheritance: Subshells, Python scripts, Node.js servers, and binaries inherit all exported variables.

One-Shot Environment Passing: `PORT=3000 node server.js` sets PORT for that single command only without polluting shell state.

printenv Specific Lookup: `printenv HOME` queries specific values instantly.

Common Beginner Traps & How to Fix Them

Mistake:Setting `API_KEY="secret"` in bash and wondering why a Python script `os.getenv("API_KEY")` returns None.

Why it happens: Without `export`, the variable is local to the shell and not passed to child processes.

How to fix: Write `export API_KEY="secret"`.

Pro Tip: Use `env -i /bin/bash --noprofile --norc` to spawn a completely clean, pristine shell session with zero inherited environment pollution.

Live Interactive Example

Hit Run Code to see it live

Exporting Variables and Sourcing .env Files

Git 2.45 / CLI

Output Console

Click "Run Code" to view the rendered output.

How it works: set -a auto-exported all variables in the .env file so the child subshell inherited them.

Your Turn: Micro Challenge

No pressure! Edit the starter code below and test your solution with instant feedback.

Micro Exercise

Export and Print an Environment Variable

Export `export PLATFORM="ZenCompiler"`.
Print it from a child subshell using `bash -c 'echo "Platform: $PLATFORM"'`.

Sandbox Output

Click "Run & Check" to test your solution.

Finished reading and practicing?

Mark this lesson as completed to update your course progress.