← All projects

Part 12 of this project

Deploy

Prepare Harborline Digest for production hosting.

Goal

This snapshot advances Harborline Digest by teaching you to prepare Harborline Digest for production hosting.

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 Docker for Postgres stages.

Port 3003 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 HTTPS cookies, a strong SESSION_SECRET, and env-only database URLs.

Keep server routes thin: pages present data, server handlers enforce rules, and templates escape output by default.

Walkthrough

Review deploy docs; never commit .env.

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

SESSION_HTTPS_ONLY=true
DATABASE_URL=postgres://...

Run and verify

Enter 12-Deploy, install dependencies, copy .env.example, and start Nuxt on port 3003.

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

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

Troubleshooting

If sessions vanish after deploy, check HTTPS cookie settings.

For database failures, confirm Docker/Wrangler and the harborline_NN name when applicable. Never commit .env or node_modules.

  • Read the first error first
  • Restart after environment changes
  • Never commit secrets

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

Related tutorials