Retro — bahalaka.com Deploy
What Happened
Full GO chain: ~P → ~E → /~B ~T ~F/ → ~S → ~R. Planned, estimated, built, tested, shipped, and retro'd the deployment of bahalaka.com to Cloudflare Pages. 17 commits from initial plan to live site.
What Went Well
Smooth Deploy
- Cloudflare Pages project created and deployed in one pass
- Custom domain (bahalaka.com + www) active immediately — no DNS propagation wait
- SSL auto-provisioned by Cloudflare edge
- All smoke + functional tests passed first try
- Static site, no build step — wrangler just uploads the file
Plan Evolution
- Plan iterated 8 times (v1→v4 app plan + website plan + deploy plan) — each iteration added depth
- Agreement system went through 3 rewrites to get the perspective right
- Nous C inventory mapped 22 existing modules — huge leverage for future build
What Could Be Better
Token Permissions
- DNS API token (cfat_) couldn't add Pages custom domains — had to use wrangler's OAuth token directly
- For future: create a single API token with both DNS:Edit AND Pages:Write scopes
No Remote Repo
- bahalaka repo is local-only — no GitHub remote yet
- For production: create GitHub repo and push for backup + collaboration
Tool Failures
None. All wrangler and curl commands succeeded.
Permission Issues
cfat_ token lacked Pages domain write permission. Resolved by using wrangler OAuth token for the Pages API call.
Performance Notes
Deploy was fast — 2.46s upload for the single file. DNS resolution was near-instant thanks to Cloudflare's edge network.
Commitments
- Create a GitHub remote for the bahalaka repo
- Create a unified Cloudflare API token with DNS + Pages scopes for future deploys
- Future redeploys:
wrangler pages deploy site/ --project-name bahalaka --branch main --commit-dirty=true