1

Development

Sulthan Zaki edited this page 2026-07-26 20:39:31 +07:00

Table of Contents

• Development
• Backend
• Local stack
• Userscript iteration
• Relevant skills
• Design docs

Development

Backend

cd backend
go test ./...                          # unit + handler tests
go test -run TestName ./...            # single test
CGO_ENABLED=0 go build                 # static binary (needed for the distroless image)

Local stack

docker compose up            # named volume mounted at /data, restart: unless-stopped

Uses docker-compose.yml only (no Traefik override, no host domain needed) — binds 127.0.0.1:8080.

Userscript iteration

The file is GM_*-free, so install the same unmodified file in desktop Tampermonkey/Violentmonkey for faster iteration than round-tripping through a phone. Point API_BASE at a local/dev backend while testing.

Relevant skills

multi-stage-dockerfile and docker-compose-orchestration cover the container patterns used in backend/Dockerfile and the compose files.

Design docs

Each non-trivial feature has a plan/spec written before implementation:

• plans/mangaBookmark.md — original spec, still the source of truth for scope and constraints.
• plans/2026-07-25-bookmark-implementation-plan.md
• plans/2026-07-25-bookmark-list-favorites-design.md — the updated_at ordering rule, in full.
• plans/2026-07-25-web-ui-implementation-plan.md
• plans/2026-07-26-server-latest-chapter-polling.md
• docs/superpowers/specs/ — design docs for web UI and the latest-chapter poller.

Read the relevant plan before changing behaviour it describes — it usually records why, not just what.