Deploy

Goal

This snapshot advances Saltmarsh Daily by teaching you to prepare Saltmarsh Daily for Deno Deploy.

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

Prerequisites

Use Deno 2+ and a code editor. No Docker is required — each snapshot uses its own SQLite file.

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

• Deno runtime
• A code editor and terminal

Concepts

Production needs HTTPS cookies, a strong SESSION_SECRET, and env-only secrets.

Keep handlers thin: routes present data, server logic enforces rules, and Fresh escapes JSX 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_PATH=/data/saltmarsh.db

Run and verify

Enter 12-Deploy, install deps, copy .env.example, and start Fresh on port 8003.

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

git clone https://github.com/michaeldunga1/fcc-fresh-blog.git
cd fcc-fresh-blog/12-Deploy
deno install
cp .env.example .env
deno task start

Troubleshooting

If sessions vanish after deploy, check HTTPS cookie settings.

For SQLite failures, confirm DATABASE_PATH and write permissions. Never commit .env or the .db file.

• 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