Environment Variables

Look, if you've ever dealt with this in production, you know exactly what the problem is. Applications require configuration. Passwords, API keys, and database URLs change depending on whether you are running locally or in production. Hardcoding these into your code or Dockerfile is a massive security risk. Instead, we use Environment Variables. In the CLI, you pass these using the -e flag (-e POSTGRES_PASSWORD=secret). In Docker Compose, you declare them under the environment: key. This isn't just academic theory—understanding the *why* behind this is what separates junior devs from senior engineers. When you deploy to a cluster, this is the mechanic that prevents catastrophic failure.

Look, if you've ever dealt with this in production, you know exactly what the problem is. Writing passwords directly into docker-compose.yml is slightly better than hardcoding them in code, but it is still terrible. You commit the YAML to Git, which means your passwords are now public. To fix this, you put your secrets in a separate file named .env, and you tell Git to ignore it. Docker Compose automatically reads the .env file and allows you to inject those secrets dynamically using string interpolation: ${VARIABLE}. This isn't just academic theory—understanding the *why* behind this is what separates junior devs from senior engineers. When you deploy to a cluster, this is the mechanic that prevents catastrophic failure.

Look, if you've ever dealt with this in production, you know exactly what the problem is. Sometimes, your API requires 30 different environment variables. Typing - ${KEY1}, - ${KEY2} in the YAML file 30 times is exhausting. Instead of mapping them one by one, you can use the env_file: directive. This tells Compose to grab an entire file (like .env.production) and blindly inject every single key-value pair inside it directly into the container. This keeps your YAML file incredibly clean. This isn't just academic theory—understanding the *why* behind this is what separates junior devs from senior engineers. When you deploy to a cluster, this is the mechanic that prevents catastrophic failure.

Environment Variables. Applications require configuration. Passwords, API keys, and database URLs change depending on whether you are running locally or in production. Hardcoding these into your code or Dockerfile is a massive security risk. Instead, we use Environment Variables. In the CLI, you pass these using the -e flag (-e POSTGRES_PASSWORD=secret). In Docker Compose, you declare them under the environment: key.

The .env File. Writing passwords directly into docker-compose.yml is slightly better than hardcoding them in code, but it is still terrible. You commit the YAML to Git, which means your passwords are now public. To fix this, you put your secrets in a separate file named .env, and you tell Git to ignore it. Docker Compose automatically reads the .env file and allows you to inject those secrets dynamically using string interpolation: ${VARIABLE}.

Why should you use string interpolation (e.g., ${DB_PASSWORD}) inside your docker-compose.yml file rather than writing the password out as plain text?

• →Because the docker-compose.yml file is committed to Git. By using interpolation, you keep the actual passwords safely hidden in a .env file that Git ignores.
• →Because interpolation makes Docker Compose boot up faster.

Bulk Injection (env_file). Sometimes, your API requires 30 different environment variables. Typing - ${KEY1}, - ${KEY2} in the YAML file 30 times is exhausting. Instead of mapping them one by one, you can use the env_file: directive. This tells Compose to grab an entire file (like .env.production) and blindly inject every single key-value pair inside it directly into the container. This keeps your YAML file incredibly clean.

Hierarchy of Precedence. What happens if you define PORT=3000 in the .env file, but you define PORT=8080 directly in the environment: section of the YAML file? Docker Compose follows a strict 'Hierarchy of Precedence'. Values hardcoded directly in the YAML environment: section ALWAYS override values pulled from an env_file:. And command-line variables (if you pass them manually) override everything. Knowing this prevents debugging nightmares.

You want to supply 40 different environment variables to your backend-worker container. Instead of listing all 40 manually in the docker-compose.yml, what is the cleanest approach?

• →Create a separate .env file containing the 40 variables, and use the env_file: [ ".env" ] directive to inject them all at once.
• →Write a bash script to run docker exec 40 times.

Configuration Mastered. You have mastered configuration management in Docker Compose. You understand the critical security importance of separating secrets from infrastructure code using .env files. You know how to use interpolation and the env_file: directive to keep your YAML clean. Next, we will tackle the most complex orchestration challenge: forcing containers to boot in a specific, strict order.