Track project · 16

Release TaskFlow

Package the API, verify it in CI, deploy API + web, and prove the production release with smoke tests and rollback notes.

Build plan

Work through it one observable step at a time

01
Write a simple Dockerfile, build it, then improve caching and runtime size.
02
Run API + PostgreSQL in Compose and fix the `localhost` networking mistake intentionally.
03
Create a pull-request CI workflow with checkout, deterministic pnpm install, typecheck, tests, and build.
04
Set workflow token permissions to the minimum required.
05
Add concurrency/branch protection so obsolete or failing changes do not release.
06
Document the production migration step and compatibility requirement.
07
Deploy the API and verify health/readiness.
08
Deploy Next.js to Vercel with production API configuration.
09
Verify production CORS, DNS, and TLS.
10
Run post-deploy smoke tests and inspect logs/metrics.
11
Write and rehearse the rollback decision/runbook.

Evidence

Do not rely on “it seems to work”

Evidence to collect

A clean Git diff or file-tree changeCommands used and their exit/resultBrowser, HTTP, database, test, container, or CI evidence that proves the behaviorOne deliberate failure, the evidence you used, and the root-cause fixA short explanation of why the final responsibility lives in the chosen layer

Project exit ticket

Close the project only when these are true

Completion

I can demonstrate every deliverable.I can reproduce one key part without the walkthrough.I can explain one trade-off I deliberately chose.I can show one failure that my tests, constraints, or runbook now protects against.