Deploy

Goal

This snapshot advances Cedarline Post by teaching you to prepare Cedarline Post for Fly.io or Render with a persistent SQLite volume.

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

Prerequisites

Use Go 1.22+, a terminal, and a code editor. You should recognize packages, functions, and HTTP verbs.

Port 8081 must be free. Copy .env.example before starting. Stages from the data layer use a per-snapshot SQLite file (no Docker required).

• Go 1.22 or newer
• A code editor and terminal
• Optional: Docker only if you prefer another database later

Concepts

Production needs HTTPS-only cookies, a strong SESSION_SECRET, and an environment-only database path on durable storage.

Keep handlers thin: routes accept input, SQL and helpers enforce rules, and html/template escapes output by default.

Walkthrough

Review render.yaml (or Fly volume notes), set SESSION_SECRET and APP_URL, 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.example.com
DATABASE_PATH=/var/data/cedarline.db

Run and verify

Enter 12-Deploy, copy .env.example, run go mod tidy, and start the server on port 8081.

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

git clone https://github.com/michaeldunga1/fcc-go-blog.git
cd fcc-go-blog/12-Deploy
cp .env.example .env
go mod tidy
go run .

Troubleshooting

If sessions vanish after deploy, check HTTPS-only cookie settings behind a proxy.

Missing module errors usually mean go mod tidy was not run in this snapshot. For SQLite failures, delete a corrupt *.db file and restart so migrate/seed can recreate it.

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

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