← All projects

Pagination and Search

Paginate the feed and search post text.

Goal

This snapshot advances Cedarline Post by teaching you to paginate the feed and search post text.

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

Pagination bounds work per page. Search filters with LIKE before slicing to page size 5.

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

Walkthrough

Use page size 5, compute total pages, and accept a q query parameter.

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

pageSize := 5
pages := (len(all) + pageSize - 1) / pageSize

Run and verify

Enter 10-Pagination-And-Search, 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/10-Pagination-And-Search
cp .env.example .env
go mod tidy
go run .

Troubleshooting

Off-by-one errors often come from mixing 0-based offsets with 1-based page numbers.

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

Search for ownership and confirm matching cards.

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