[Epic] Phase 2 — Git-native application delivery

[chrisbbreuer]

Parent

#132

Outcome

Provide an end-to-end path from repository or container source to a running application: connect source, choose a build strategy, configure environment/domain/health, deploy through a durable queue, inspect live progress, create previews, and promote or roll back a release.

Product scope

• GitHub, GitLab, Bitbucket, Gitea, and generic Git/SSH connections.
• Dockerfile, buildpack-style detection, static output, prebuilt image, and multi-service Compose paths.
• Secure webhook-driven auto-deploy and branch/monorepo controls.
• Durable deployment history, cancellation, retry, concurrency, promotion, and rollback.
• Pull-request previews with stable URLs and automatic cleanup.

Existing work incorporated

• Test deploy: paweldregan.com — keep CloudFront/S3 frontend, add Lambda-backed /api #117
• Deploy a full-stack containerized backend (API + DB + queues + mail + cache) on ECS Fargate, fronted by an existing CloudFront/S3 site #118

Children

• Add Git provider connections and secure webhook-based auto-deploy #146
• Build a guided application/import wizard with pluggable build strategies #147
• Add a durable deployment queue with live logs, cancellation, retries, and concurrency controls #148
• Ship pull-request and branch preview environments with TTL cleanup #149
• Support first-class Docker Compose services and one-click templates #150
• Unify releases, promotion, zero-downtime deployment, and rollback #151

Exit criteria

A new user can deploy a representative server app, static site, serverless app, container image, and Compose stack without hand-editing generated state, while an expert can reproduce the same result through the CLI/API.