Routing

Goal

This snapshot advances Cedarline Post by teaching you to organize page routes with Chi.

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

Chi groups related endpoints with a readable router. Path patterns and methods both matter.

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

Walkthrough

Mount home, about, and health routes on a Chi router and start the server from main.

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

r := chi.NewRouter()
r.Get("/", home)
r.Get("/about", about)
r.Get("/health", health)

Run and verify

Enter 02-Routing, 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/02-Routing
cp .env.example .env
go mod tidy
go run .

Troubleshooting

A missing route registration leaves the path undefined. Check both path and HTTP method.

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

Add a /contact plain-text route.

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