Sha256: 35eab33092b5e863535c5673b0d3e5114f6e5531578833f2fd02f7859c741254

Contents?: true

Size: 1.02 KB

Versions: 1

Compression:

Stored size: 1.02 KB

Contents

---
title: Run in Pieces
nav_order: 36
---

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.

```bash
ufo docker build
ufo docker push # pushes last built image to a registry
```

Build the task definitions.

```bash
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.

```bash
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

1 entries across 1 versions & 1 rubygems

Version Path
ufo-4.4.3 docs/_docs/more/run-in-pieces.md