Cloud Infrastructure Deployment

Cloud Deployment

Current cloud surfaces deploy on Cloudflare, not the monorepo ECS/Fargate/Cognito stack.

Surface	Repo	Deploy model
Portal API	api.trackdub	Wrangler → Cloudflare Workers + D1 + R2
Portal SPA	portal.trackdub	Static/SPA host (see that repo's CI/README)
Marketing	trackdub.com	Site host (Lovable-connected; avoid force-pushing history)

The desktop app is not a cloud-deployed services; they ship as local .NET apps / libraries.

api.trackdub (Worker)

1. Create D1 database; set database_id in wrangler.jsonc
2. Create R2 bucket for the MEDIA binding
3. Set secrets: BETTER_AUTH_SECRET, ADMIN_API_TOKEN
4. Set public vars: APP_ENV, PORTAL_ORIGIN (exact portal origin)
5. npm run db:migrate:remote
6. npm run deploy
7. Custom domain api.trackdub.com via Wrangler routes

Verify:

curl https://api.trackdub.com/api/health
curl https://api.trackdub.com/api/version

Bootstrap first operator via POST /api/admin/invite with Authorization: Bearer $ADMIN_API_TOKEN (see API README).

What not to follow

Do not use these as current deploy docs:

• ECS Fargate API + GPU workers
• infra/phase-0-bootstrap-aws.ps1 / OIDC to personal GitHub orgs
• Amplify + Cognito for frontend/
• EFS ONNX caches for a C# API host

Those belong to Trackdub-Monorepo-Archive and older wiki drafts.

Related

• Cloud-API-and-Job-Management
• Web-Dashboard
• Desktop CI: .github/workflows in Trackdub-gated
• Pipeline/Sdk CI: .github/workflows in Trackdub