Stacktape offers multiple ways to deploy your application. Choose based on your workflow.
CLI Deployment
Deploy directly from your terminal:
Required Options
| Option | Description | Example |
|---|---|---|
--stage | Environment name | dev, staging, production |
--region | AWS region | us-east-1, eu-west-1 |
The project name is taken from your config file or can be specified with --projectName.
Deployment Process
- Build - Code is packaged (container images or Lambda bundles)
- Upload - Artifacts uploaded to S3/ECR
- Deploy - CloudFormation creates/updates resources
- Verify - Health checks confirm deployment success
If deployment fails, it automatically rolls back to the last working state.
Hot-Swap Deployments
When only your code changes (not infrastructure), use hot-swap for faster deployments:
Hot-swap updates Lambda functions and container images directly, bypassing CloudFormation. This reduces deployment time from minutes to seconds.
Web Console Deployment
Deploy through the Stacktape Console with a visual interface.
Setup
- Create a project in the console
- Connect your GitHub or GitLab repository
- Select the branch and commit to deploy
Deploying a Stage
- Navigate to your project
- Click Create new stage
- Configure:
- Branch and commit
- Stage name
- AWS account and region
- Click Deploy now
The console shows real-time deployment logs and resource status.
GitOps (CI/CD)
Automate deployments triggered by Git events.
Push-to-Branch Deployments
Automatically deploy when you push to a specific branch:
- In the console, go to your project
- Click Actions > View Git configuration
- Click Set up Push-To-Branch deployments
- Configure:
- Trigger branch (e.g.,
main) - Target stage (e.g.,
production) - AWS account
- Trigger branch (e.g.,
Now every push to main automatically deploys to production.
Preview Deployments (PR Environments)
Create temporary environments for each pull request:
- Click Set up PR deployments
- Configure the default settings for preview environments
For each PR:
- A new stage is created automatically
- A comment is added to the PR with the deployment URL
- The stage is updated on each push
- The stage can be automatically deleted when the PR is merged/closed
External CI/CD
Use Stacktape in your existing CI pipeline (GitHub Actions, GitLab CI, etc.).
GitHub Actions Example
GitLab CI Example
Required Secrets
Set STACKTAPE_API_KEY in your CI/CD secrets. Get your API key from the console.
Multi-Stage Strategy
A typical deployment strategy:
| Stage | Trigger | Purpose |
|---|---|---|
dev | Manual / local | Individual developer testing |
staging | Push to develop | Integration testing |
production | Push to main | Live users |
pr-123 | Pull request | PR review environments |
Each stage is completely isolated with its own resources.
Deployment Commands
View Deployment Status
Delete a Stack
This permanently deletes all resources in the stack, including databases and their data.
View Logs
How Deployment Works
Under the hood, Stacktape:
- Compiles your config into a CloudFormation template (~30 lines becomes ~1,200+)
- Builds container images and Lambda bundles with optimized caching
- Uploads artifacts to S3 and ECR in your AWS account
- Deploys using CloudFormation with automatic rollback on failure
- Performs health checks and surfaces any errors
All resources follow AWS well-architected best practices for security, reliability, and cost optimization.