Deploy

Goal

This snapshot advances Circuit Daily by teaching you to prepare Circuit Daily for Railway and managed Postgres.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use Node.js 20+, npm, and a terminal. You should recognize TypeScript modules, decorators, and HTTP verbs.

Port 3001 must be free. Copy .env.example before starting database stages.

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

Concepts

Production needs secure cookies, a strong SESSION_SECRET, and environment-only database URLs.

Keep controllers thin: accept input, call services, render Handlebars views. Escape stays on by default in templates.

Walkthrough

Review railway notes, set DATABASE_URL and SESSION_SECRET on Railway, and never commit .env.

Read the example, then open the matching snapshot. The repository includes the surrounding setup and error handling.

SESSION_HTTPS_ONLY=true
APP_URL=https://your-app.up.railway.app

Run and verify

Enter 12-Deploy, install dependencies, copy .env.example when present, and start Nest on port 3001.

Open http://127.0.0.1:3001. Watch the terminal for validation and database errors.

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

Troubleshooting

If sessions vanish after deploy, check secure cookie settings behind a proxy.

Missing-module errors usually mean npm install ran in another snapshot. For Postgres failures, confirm Docker and the circuit_NN database name.

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

Try this

List every secret that must live only in the host environment.

Test a happy path and one invalid or unauthorized request.

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