Deployment Guide
Learn how SnapDeploy builds and deploys your applications in minutes, not hours.
How Deployment Works
When you deploy to SnapDeploy, here's what happens:
1
Code Fetch
Clone your repository from GitHub or pull your Docker image
2
Framework Detection
Analyze project structure to detect language and framework
3
Dockerfile Generation
Generate optimized Dockerfile (if not provided)
4
Image Build
Build Docker image using AWS CodeBuild
5
Deploy to ECS
Create/update ECS task and service with zero downtime
6
Health Check & Routing
Verify container is healthy, then route traffic
Deployment Methods
Deploy from GitHub
Connect your repository for automatic deployments on every push.
Deploy from Docker
Deploy any Docker image from Docker Hub or private registries.
Build Time Estimates
| Application Type | Build Time |
|---|---|
| Static site (HTML, CSS, JS) | ~15-30 seconds |
| Node.js application | ~30-45 seconds |
| Python Django/Flask | ~60-90 seconds |
| Go application | ~30-45 seconds |
| Java Spring Boot | ~60-90 seconds |
| Pre-built Docker image | ~10-20 seconds |
Deployment Triggers
-
Manual Deploy: Click "Deploy" in the dashboard
-
Git Push: Automatic deployment when you push to your configured branch
-
API: Trigger deployments via REST API for CI/CD integration
-
CLI: Deploy using
snapdeploy deploy
Zero-Downtime Deployments
SnapDeploy uses rolling deployments to ensure your application stays available:
- New container starts alongside the old one
- Health checks verify the new container is ready
- Traffic gradually shifts to the new container
- Old container is terminated after successful rollout
- Automatic rollback if health checks fail