Why Environment variables in NestJS? - Purpose & Use Cases

The Big Idea

Discover how a simple change can protect your secrets and save hours of frustrating fixes!

The Scenario

Imagine you have to change your app's database password or API keys directly inside your code every time you move from your laptop to a server.

Each time you share your code, you risk exposing sensitive information or making mistakes by forgetting to update these details.

The Problem

Hardcoding secrets in code is risky and slow.

It makes your app less secure and harder to maintain because you must change code for every environment.

Also, sharing code with secrets can cause security leaks.

The Solution

Environment variables let you keep secrets and settings outside your code.

You store them safely in separate files or system settings, and your app reads them when it runs.

This way, you can change settings without touching the code, making your app safer and easier to manage.

Before vs After

✗ Before

const dbPassword = 'mySecret123'; // hardcoded password

✓ After

const dbPassword = process.env.DB_PASSWORD; // read from environment

What It Enables

This lets your app adapt easily to different environments without code changes, keeping secrets safe and your workflow smooth.

Real Life Example

When deploying a NestJS app, you can use environment variables to set the database URL and API keys differently for your local machine, testing server, and production server without changing your code.

Key Takeaways

Hardcoding secrets is risky and inflexible.

Environment variables keep secrets outside code for safety.

They make apps easier to configure across different environments.