Sha256: 2fdf62873ed64831315984ea681f6dbf3b99235388c29d73c991b4791cc33246
Contents?: true
Size: 1 KB
Versions: 12
Compression:
Stored size: 1 KB
Contents
---
title: Run in Pieces
nav_order: 39
---
The `ufo ship` command goes through a few stages:
1. building the docker image
2. registering the task defiintions
2. updating the ECS service.
The CLI exposes many of these steps as separate commands. Here is now you would be able to run each of the steps in pieces.
Build the docker image first.
ufo docker build
ufo docker push # pushes last built image to a registry
Build the task definitions.
ufo tasks build # generates task definition json files to .ufo/output
ufo tasks register # registers all genreated task definitions .ufo/output to ECS
Update the service with the task definitions in `.ufo/output` untouched.
ufo deploy demo-web
Note if you use the `ufo deploy` you should ensure that you have already pushed the docker image to your docker registry. Or else the task will not be able to spin up because the docker image does not exist. This is one of the reasons it is recommended that you use `ufo ship`.
{% include prev_next.md %}
Version data entries
12 entries across 12 versions & 1 rubygems