Feed and Detail

Goal

This snapshot advances Cedarline Post by teaching you to build a database-backed feed and post detail pages.

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

List and detail are separate reads: the feed shows summaries; detail loads one row by primary key.

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

Walkthrough

Link feed titles to /posts/{id} and return 404 when a post is missing.

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

id, _ := strconv.Atoi(chi.URLParam(r, "id"))
post, err := getPost(id)
if err != nil { http.NotFound(w, r); return }

Run and verify

Enter 05-Feed-And-Detail, 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/05-Feed-And-Detail
cp .env.example .env
go mod tidy
go run .

Troubleshooting

Passing a non-integer id fails conversion before a useful query runs—return 404 for missing rows.

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

Show the created timestamp on the detail page.

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