Environment-based configuration in Express

Introduction

Environment-based configuration helps your app use different settings for development, testing, and production. This keeps your app flexible and safe.

You want to use a different database in development and production.

You need to hide secret keys or passwords from your code.

You want to change app behavior without changing code.

You want to easily switch between local and cloud servers.

You want to keep sensitive info out of your public code.

Syntax

Express

const express = require('express');
const app = express();

const port = process.env.PORT || 3000;
const dbUrl = process.env.DB_URL || 'mongodb://localhost/devdb';

app.listen(port, () => {
  console.log(`Server running on port ${port}`);
});

Use process.env.VARIABLE_NAME to access environment variables.

Provide default values with || to avoid errors if variables are missing.

Examples

Use the PORT environment variable if set, otherwise use 3000.

Express

const port = process.env.PORT || 3000;

Get a secret key from environment variables to keep it hidden from code.

Express

const secretKey = process.env.SECRET_KEY;

Check if the app is running in production mode.

Express

const isProduction = process.env.NODE_ENV === 'production';

Sample Program

This Express app uses environment variables for the port and a welcome message. If you set PORT or WELCOME_MESSAGE in your environment, the app uses those. Otherwise, it uses default values.

Try running this app with different environment variables to see how it changes.

Express

const express = require('express');
const app = express();

// Use environment variables or defaults
const port = process.env.PORT || 3000;
const message = process.env.WELCOME_MESSAGE || 'Hello from Express!';

app.get('/', (req, res) => {
  res.send(message);
});

app.listen(port, () => {
  console.log(`Server running on port ${port}`);
});

Important Notes

Set environment variables outside your code, for example in a terminal or a .env file.

Never commit secret keys or passwords to your code repository.

Use packages like dotenv to load environment variables from a file during development.

Summary

Environment-based configuration lets your app change settings without code changes.

Use process.env to access environment variables in Express.

Always provide safe defaults and keep secrets out of your code.

Practice

1. What is the main purpose of using environment-based configuration in an Express app?

easy

A. To change app settings without modifying the code

B. To write all configuration directly inside the code

C. To make the app run only on one specific machine

D. To avoid using any external files or variables

Solution

1. Step 1: Understand environment-based configuration

   It allows changing settings like ports or database URLs without changing the app code.

2. Step 2: Compare options

   Only To change app settings without modifying the code describes this purpose correctly; others contradict the idea of flexible configuration.

3. Final Answer:

   To change app settings without modifying the code -> Option A

4. Quick Check:

   Environment config = change settings without code [OK]

Hint: Think: config changes without code edits [OK]

Common Mistakes:

• Confusing environment config with hardcoded settings
• Thinking environment config restricts app to one machine
• Assuming environment config means no external variables

2. Which of the following is the correct way to access an environment variable named PORT in an Express app?

easy

A. const port = process.env.PORT;

B. const port = env.PORT;

C. const port = process.PORT;

D. const port = process.env['port'];

Solution

1. Step 1: Recall how to access environment variables in Node.js

   Use process.env.VARIABLE_NAME to get environment variables.

2. Step 2: Check each option

   const port = process.env.PORT; uses the correct syntax. const port = env.PORT; misses process. const port = process.PORT; uses wrong property. const port = process.env['port']; uses lowercase key which is case-sensitive and usually environment variables are uppercase.

3. Final Answer:

   const port = process.env.PORT; -> Option A

4. Quick Check:

   Use process.env.VAR to access env variables [OK]

Hint: Always use process.env.VAR to get env variables [OK]

Common Mistakes:

• Omitting 'process' before 'env'
• Using wrong casing for environment variable names
• Accessing environment variables as properties of process

3. Consider this Express code snippet:

const port = process.env.PORT || 3000;
app.listen(port, () => {
  console.log(`Server running on port ${port}`);
});

If the environment variable PORT is set to 5000, what will be printed when the server starts?

medium

A. Server running on port process.env.PORT

B. Server running on port 3000

C. Server running on port undefined

D. Server running on port 5000

Solution

1. Step 1: Understand the fallback logic

   The code uses process.env.PORT || 3000, so if PORT is set, it uses that; otherwise, 3000.

2. Step 2: Apply given environment variable

   Since PORT is set to 5000, the server listens on port 5000 and prints that.

3. Final Answer:

   Server running on port 5000 -> Option D

4. Quick Check:

   Env var set? Use it; else default [OK]

Hint: If env var exists, use it; else fallback [OK]

Common Mistakes:

• Ignoring the environment variable and using default
• Printing the variable name instead of its value
• Assuming undefined if environment variable exists

4. You wrote this code to read a secret key:

const secret = process.env.SECRET_KEY;
console.log(secret.length);

But when you run the app, it crashes with TypeError: Cannot read property 'length' of undefined. What is the likely cause?

medium

A. You must use process.SECRET_KEY instead of process.env.SECRET_KEY

B. The secret key is empty string, so length is undefined

C. The environment variable SECRET_KEY is not set

D. You need to convert secret to a string before accessing length

Solution

1. Step 1: Analyze the error message

   The error says length is accessed on undefined, meaning secret is undefined.

2. Step 2: Check environment variable usage

   If SECRET_KEY is not set in environment, process.env.SECRET_KEY is undefined, causing the error.

3. Final Answer:

   The environment variable SECRET_KEY is not set -> Option C

4. Quick Check:

   Undefined env var causes undefined value [OK]

Hint: Check if env variable is set before using it [OK]

Common Mistakes:

• Assuming env variable is always defined
• Using wrong property to access env variables
• Not handling undefined values before property access

5. You want to configure your Express app to use different database URLs for development and production environments. Which approach correctly uses environment variables and safe defaults?

hard

A. const dbUrl = process.env.DB_URL && 'mongodb://localhost/devdb';

B. const dbUrl = process.env.DB_URL || 'mongodb://localhost/devdb';

C. const dbUrl = 'mongodb://localhost/devdb'; if (process.env.NODE_ENV === 'production') dbUrl = process.env.DB_URL;

D. const dbUrl = process.env.DB_URL ? 'mongodb://localhost/devdb' : process.env.DB_URL;

Solution

1. Step 1: Understand environment-based config with fallback

   Use environment variable if set; otherwise, use a safe default URL.

2. Step 2: Evaluate each option

   const dbUrl = process.env.DB_URL || 'mongodb://localhost/devdb'; correctly uses process.env.DB_URL || default. const dbUrl = 'mongodb://localhost/devdb'; if (process.env.NODE_ENV === 'production') dbUrl = process.env.DB_URL; tries to reassign a const variable (error). const dbUrl = process.env.DB_URL && 'mongodb://localhost/devdb'; uses && which returns false if DB_URL is missing. const dbUrl = process.env.DB_URL ? 'mongodb://localhost/devdb' : process.env.DB_URL; reverses the condition, causing wrong assignment.

3. Final Answer:

   const dbUrl = process.env.DB_URL || 'mongodb://localhost/devdb'; -> Option B

4. Quick Check:

   Use env var or fallback default [OK]

Hint: Use env var OR fallback default with || [OK]

Common Mistakes:

• Reassigning const variables
• Using && instead of || for fallback
• Swapping condition logic causing wrong URL