Getting Started

Goal

This snapshot advances Copperline Journal by teaching you to create a minimal Express server on port 3000.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder to see the new responsibility clearly.

Prerequisites

Use Node.js 20 or newer, npm, and a terminal. You should recognize basic JavaScript functions, objects, and HTTP requests.

Port 3000 must be available. MongoDB snapshots use Docker locally; copy the example environment file before starting them.

• Node.js and npm installed
• A code editor and terminal
• Docker from part 4 onward

Concepts

Express wraps Node's HTTP server with an application object and readable route methods.

Keep responsibilities visible: middleware prepares requests, routes choose handlers, models protect data rules, and EJS views present escaped values.

Walkthrough

Create the app, register a root GET route, and listen on the environment port with a 3000 fallback.

Read the example from input to output, then inspect the matching snapshot. The repository includes the surrounding setup and error handling.

const express = require("express");
const app = express();
app.get("/", (_req, res) => res.send("Copperline Journal is live"));
app.listen(process.env.PORT || 3000);

Run and verify

Enter 01-Getting-Started, install its dependencies, copy .env.example when present, and start the server.

Open http://localhost:3000. Keep the terminal visible so route, validation, and database errors can be connected to the browser action that caused them.

git clone https://github.com/michaeldunga1/fcc-express-blog.git
cd fcc-express-blog/01-Getting-Started
npm install
cp .env.example .env
npm start

Troubleshooting

If the browser cannot connect, confirm the process is still running. EADDRINUSE means another process owns port 3000.

A missing-module error usually means npm install ran in another snapshot. For database failures, check the container and that this folder uses its own Copperline database name.

• Read the first error first
• Restart after environment changes
• Never commit .env or node_modules

Try this

Add a /health route that returns { "ok": true }.

Test a happy path and one invalid or unauthorized request. Useful applications return clear feedback without exposing secrets or stack traces.

• Make one small change
• Test it in the browser
• Compare with the next snapshot only after it works