← All projects

Deploy

Prepare Canopy Journal for Railway and managed Postgres.

Goal

This snapshot advances Canopy Journal by teaching you to prepare Canopy Journal 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 Docker for Postgres stages. You should recognize async functions and HTTP verbs.

Port 3002 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 APP_KEY, and env-only database URLs.

Keep controllers thin: routes accept input, Lucid models enforce rules, and Edge escapes 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\nAPP_URL=https://your-app.up.railway.app

Run and verify

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

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

docker compose up -d
git clone https://github.com/michaeldunga1/fcc-adonis-blog.git
cd fcc-adonis-blog/12-Deploy
npm install
cp .env.example .env
node ace serve --watch

Troubleshooting

If sessions vanish after deploy, check HTTPS cookie settings.

For database failures, confirm Docker and the canopy_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