Architecture: How should docs-angular be deployed to Cloudflare Pages in a...
Documentation for Sessions
🏗️ Architecture: How should docs-angular be deployed to Cloudflare Pages in a...
Date: 2026-01-28
Time: 18:48:36 UTC
Session: editor2-73.4
Agent: orchestrator
Confidence: 95%
Status: ✅ Documented
📋 Decision Context
Question:
How should docs-angular be deployed to Cloudflare Pages in a monorepo?
Task: Set up reliable deployment pipeline for docs.gograb.space
🎯 Decision Made
Chosen:
GitHub Actions workflow with wrangler direct upload, NOT Cloudflare Git integration
Options Considered:
- GitHub Actions with wrangler deploy
- Cloudflare automatic Git integration
- Manual wrangler CLI deploys
💭 Reasoning
Cloudflare Git integration has issues with monorepos: 1) Rebuilds entire repo on every push, 2) Branch names with slashes (deploy/docs) can break Git integration ("No Git connection" error), 3) Less control over build process, 4) Opaque debugging. GitHub Actions provides full control, only builds docs-angular, has visible logs, and works reliably with any branch naming convention.
📁 Files Involved
.github/workflows/deploy-docs.yml
🔗 Related
- Decision ID:
dev_1769626113243_cooe2q7 - Session: 73
- Workspace: editor2
Auto-generated by MCP Smart Consolidation