Overview

How it works

Build a container image and upload it to the Elastic Container Registry (ECR) associated with the app, that is created by Tapitalee.

Create a new deploy within Tapitalee which tells ECS Fargate to replace the existing running container image with the new one. If any errors occur, it rolls back to the old one.

Alternatively, you can configure a process to use a third-party pre-built image (e.g. nginx:latest) instead of building your own — see Deploying from the CLI → Third-party images.

Ways to deploy

You can upload images to the ECR yourself and then deploy via the Tapitalee web UI, or initiate a deploy via the tapit CLI tool.

Via the Web UI

Once you have built and pushed your image to the app’s ECR, you can trigger a new deployment from the Tapitalee web dashboard by selecting the image tag you wish to deploy.

Via Command Line

The tapit CLI tool can assist with the complete build and upload process — from building the container image through to triggering the deployment. The simplest approach is:

tapit image deploy

which handles everything in one step — building the image, pushing it to the app’s ECR, and triggering the deployment.

You can check the result of a deployment with:

tapit show deploy
tapit list deploys

or by looking at the Deploys page for your app in the web UI.

See Via Command Line for details.