Deploy

Goal

This snapshot advances Copperline Journal by teaching you to prepare Copperline Journal for Render and MongoDB Atlas.

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

Production uses managed MongoDB, stable environment secrets, trusted proxies, secure cookies, durable media, and real SMTP.

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

Walkthrough

Create Atlas and Render services, set environment variables, use the assigned PORT, trust one proxy, and verify the health and account flows.

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

if (process.env.NODE_ENV === "production") app.set("trust proxy", 1);
const port = process.env.PORT || 3000;

Run and verify

Enter 12-Deploy, 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.

docker compose up -d
git clone https://github.com/michaeldunga1/fcc-express-blog.git
cd fcc-express-blog/12-Deploy
npm install
cp .env.example .env
npm start
# optional: npm run seed

Troubleshooting

A deploy that builds but does not boot commonly has a missing variable, blocked Atlas network access, or an incorrect start command.

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

Deploy, register a new account, sign in from a fresh browser, and complete one password reset.

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