Configuration management in Deno - Mini Project: Build & Apply

Configuration Management in Deno

📖 Scenario: You are building a simple Deno application that needs to manage configuration settings for connecting to a database. These settings include the database host, port, username, and password.Managing configuration properly helps keep your code clean and makes it easy to change settings without touching the main logic.

🎯 Goal: Create a configuration object in Deno, add a helper variable for the connection string, use the configuration to build a connection URL, and export the final configuration for use in other parts of the app.

📋 What You'll Learn

Create a configuration object with exact keys and values

Add a helper variable to build a connection string

Use the configuration object to create a full database URL

Export the final configuration object

💡 Why This Matters

🌍 Real World

Managing configuration settings is essential in real applications to keep sensitive data like passwords separate and to easily change settings without modifying core logic.

💼 Career

Understanding configuration management is important for backend developers, DevOps engineers, and anyone working with server-side applications or deployment pipelines.

1

Create the configuration object

Create a constant called config that is an object with these exact properties and values: host set to "localhost", port set to 5432, username set to "admin", and password set to "secret".

Deno

# Your code here

Hint

Use const config = {} and add the properties inside the curly braces.

2

Add a helper variable for the connection string

Add a constant called connectionString that combines config.host and config.port into a string formatted as "host:port" using a template literal.

Deno

const config = {
  host: "localhost",
  port: 5432,
  username: "admin",
  password: "secret"
};

# Your code here

Hint

Use backticks ` and ${} to insert variables inside the string.

3

Create the full database URL

Create a constant called databaseUrl that uses a template literal to combine config.username, config.password, and connectionString into the format "postgres://username:password@host:port".

Deno

const config = {
  host: "localhost",
  port: 5432,
  username: "admin",
  password: "secret"
};

const connectionString = `${config.host}:${config.port}`;

# Your code here

Hint

Use a template literal with all parts combined in the correct order.

4

Export the final configuration

Export a constant called finalConfig that is an object containing databaseUrl and the original config object.

Deno

const config = {
  host: "localhost",
  port: 5432,
  username: "admin",
  password: "secret"
};

const connectionString = `${config.host}:${config.port}`;

const databaseUrl = `postgres://${config.username}:${config.password}@${connectionString}`;

# Your code here

Hint

Use export const finalConfig = { databaseUrl, config }; to export the object.

Practice

1. What is the main purpose of configuration management in a Deno application?

easy

A. To separate settings like API keys from the main code for flexibility and security

B. To write all code and settings in a single file for simplicity

C. To hardcode secret keys directly in the source code

D. To avoid using environment variables altogether

Solution

1. Step 1: Understand configuration management role

   Configuration management separates settings from code to keep apps flexible and secure.

2. Step 2: Identify correct practice in Deno

   Using environment variables or .env files keeps secrets out of code and allows easy changes.

3. Final Answer:

   To separate settings like API keys from the main code for flexibility and security -> Option A

4. Quick Check:

   Config management = separate settings [OK]

Hint: Remember: keep secrets out of code, use config files [OK]

Common Mistakes:

• Hardcoding secrets in source code
• Mixing code and settings in one file
• Ignoring environment-specific configs

2. Which of the following is the correct way to load environment variables from a .env file in Deno?

easy

A. require('dotenv').config();

B. import { config } from "https://deno.land/std/dotenv/mod.ts"; const env = config();

C. import dotenv from "dotenv"; dotenv.load();

D. import { loadEnv } from "deno_env"; loadEnv();

Solution

1. Step 1: Identify Deno's dotenv import syntax

   Deno uses ES module imports from URLs, like importing config from std/dotenv.

2. Step 2: Check correct usage

   Calling config() loads environment variables from .env file correctly in Deno.

3. Final Answer:

   import { config } from "https://deno.land/std/dotenv/mod.ts"; const env = config(); -> Option B

4. Quick Check:

   Deno dotenv import = import { config } from "https://deno.land/std/dotenv/mod.ts"; const env = config(); [OK]

Hint: Use Deno's std/dotenv with ES module import [OK]

Common Mistakes:

• Using Node.js require syntax in Deno
• Using non-existent packages
• Calling wrong functions to load env

3. Given this Deno code snippet:

import { config } from "https://deno.land/std/dotenv/mod.ts";
const env = config();
console.log(env.API_KEY);

If the .env file contains API_KEY=12345, what will be printed?

medium

A. undefined

B. Error: .env file not found

C. API_KEY

D. 12345

Solution

1. Step 1: Understand config() output

   The config() function reads .env and returns an object with keys and values.

2. Step 2: Access API_KEY value

   env.API_KEY accesses the value '12345' from the loaded environment variables.

3. Final Answer:

   12345 -> Option D

4. Quick Check:

   env.API_KEY = '12345' [OK]

Hint: config() returns env vars as object keys [OK]

Common Mistakes:

• Expecting config() to print keys directly
• Forgetting to create .env file
• Assuming env variables are undefined

4. What is wrong with this Deno code snippet for loading environment variables?

import { config } from "https://deno.land/std/dotenv/mod.ts";
const env = config;
console.log(env.API_SECRET);

medium

A. config is not imported correctly

B. API_SECRET is not a valid environment variable name

C. config is assigned without calling it as a function

D. console.log syntax is incorrect

Solution

1. Step 1: Check how config is used

   config is a function and must be called with parentheses to load env variables.

2. Step 2: Identify the error

   Assigning config without () means env is the function itself, not the loaded object.

3. Final Answer:

   config is assigned without calling it as a function -> Option C

4. Quick Check:

   Call config() to load env [OK]

Hint: Always call config() with parentheses [OK]

Common Mistakes:

• Assigning function reference instead of calling it
• Misspelling config import
• Using wrong variable names

5. You want to manage different configurations for development and production in a Deno app. Which approach is best practice?

hard

A. Use separate .env files like .env.development and .env.production and load the correct one based on an environment variable

B. Hardcode production secrets in the code and use .env only for development

C. Use a single .env file with all keys and comment out unused ones manually

D. Store all secrets in a JSON file checked into version control

Solution

1. Step 1: Understand environment-specific configs

   Different environments need different settings to avoid mistakes and leaks.

2. Step 2: Choose best practice for Deno

   Using separate .env files and loading based on an environment variable keeps configs clean and secure.

3. Final Answer:

   Use separate .env files like .env.development and .env.production and load the correct one based on an environment variable -> Option A

4. Quick Check:

   Separate env files per environment = Use separate .env files like .env.development and .env.production and load the correct one based on an environment variable [OK]

Hint: Use multiple .env files and switch by env variable [OK]

Common Mistakes:

• Hardcoding secrets in code
• Using one .env for all environments
• Checking secrets into version control