ufo 5.0.7 → 6.0.0

data/docs/_reference/ufo-docker-base.md

@@ -1,71 +0,0 @@
----
-title: ufo docker base
-reference: true
----
-
-## Usage
-
-    ufo docker base
-
-## Description
-
-Build docker image from `Dockerfile.base` and update current `Dockerfile`.
-
-The docker cache task builds a docker image using the `Dockerfile.base` file and
-updates the FROM `Dockerfile` image with the generated image from `Dockerfile.base`.
-
-## Summarized Example
-
-    ufo docker base
-    ufo docker base --no-push # do not push the image to the registry
-
-Docker image `tongueroo/demo-ufo:base-2016-10-21T15-50-57-88071f5` built.
-
-## Concept
-
-Docker is fantastic and has given developers more power and control over the OS their application runs on.  Sometimes building Docker images can be slow though.  Docker layer caching technology helps immensely to speed up the process as Docker will only rebuild layers that require rebuilding. But sometimes one little dependency changes it results in having to rebuild many layers.
-
-The `ufo docker base` commands allows you to build an Docker image from `Dockerfile.base` to be used as a cache and in the FROM instruction in the main `Dockerfile`.  This base Docker cache image technique speeds up development substantially if you have dependencies like gems in your project.  Let's say you have 20 gems in your project and are actively developing your project. You are experimenting with 3 different gems, adding and removing them while you are investigating the best gem to use.  Without the Docker image cache that already has all of your other gems installed each time you adjust `Gemfile` it would have to wait until all the gems from scratch again installed again.
-
-There are pros and cons of using this approach.  Remember there are 2 hard problems in computer science: 1. Naming and 2. Caching.  The main con about this approach is if you forget to update the base Docker image you will have cached artifacts that will not disappear unless you rebuild the base Docker image.  While some folks are completely against introducing this cache layer, some have found it being a huge win in speeding up their Docker development workflow.  If you are using this technique it is recommended that you set up some automation that rebuilds the base Docker image at least nightly.
-
-## Demo
-
-To demonstrate this command, there's a `docker-cache` branch in the [tongueroo/demo-ufo](https://github.com/tongueroo/demo-ufo/tree/docker-cache) repo.
-
- Let's see the command in action:
-
-    ufo docker base
-    Building docker image with:
-      docker build -t tongueroo/demo-ufo:base-2017-06-12T14-36-44-2af505e -f Dockerfile.base .
-      ...
-    Pushed tongueroo/demo-ufo:base-2017-06-12T14-36-44-2af505e docker image. Took 28s.
-    The Dockerfile FROM statement has been updated with the latest base image:
-      tongueroo/demo-ufo:base-2017-06-12T14-36-44-2af505e
-
-Some of the output has been excluded so we can focus on the important parts to point out. First notice that the commmand simply shells out to the docker command and calls:
-
-    docker build -t tongueroo/demo-ufo:base-2017-06-12T14-36-44-2af505e -f Dockerfile.base .
-
-It is using the docker `-f Dockerfile.base` option to build the base image.  It names the image with `tongueroo/demo-ufo:base-2017-06-12T14-36-44-2af505e`.  The image tag contains useful information: the timestamp when the image was built and the exact git sha of the code.  The image gets push to a registry immediately.
-
-## Dockerfile FROM updated
-
-Notice at the very end, the *current* `Dockerfile`'s FROM statement has been updated with the newly built base Docker image automatically.  This saves you from forgetting to copying and pasting it the `Dockerfile` yourself.
-
-If you're using a [Dockerfile.erb](https://ufoships.com/docs/extras/dockerfile-erb/), then ufo will update the `.ufo/settings/dockerfile_variables.yml` file instead.  It assumes you're using a Dockerfile.erb that looks something like this:
-
-```Dockerfile
-FROM <%= @base_image %>
-# ...
-CMD ["bin/web"]
-```
-
-
-## Options
-
-```
-[--push], [--no-push]  
-                       # Default: true
-```
-

data/docs/_reference/ufo-docker-build.md

@@ -1,91 +0,0 @@
----
-title: ufo docker build
-reference: true
----
-
-## Usage
-
-    ufo docker build
-
-## Description
-
-Build docker image.
-
-The `ufo docker build` builds a Docker image using the Dockerfile in the current project folder.  This simply is a wrapper command that shells out and calls the `docker` command.  We're use the [tongueroo/demo-ufo](https://github.com/tongueroo/demo-ufo) project and it's Dockerfile for demonstration.  Example:
-
-    ufo docker build
-
-You'll see that it calls:
-
-    docker build -t tongueroo/demo-ufo:ufo-2017-06-11T22-18-03-a18aa30 -f Dockerfile .
-
-You should see similar output (some of the output has been truncated for conciseness):
-
-    $ ufo docker build
-    Building docker image with:
-      docker build -t tongueroo/demo-ufo:ufo-2017-06-11T22-18-03-a18aa30 -f Dockerfile .
-    Sending build context to Docker daemon 734.2 kB
-    Step 1 : FROM ruby:2.3.3
-     ---> 0e1db669d557
-    Step 2 : RUN apt-get update &&   apt-get install -y     build-essential     nodejs &&   rm -rf /var/lib/apt/lists/* && apt-get clean && apt-get purge
-     ---> Using cache
-     ---> 931ace833716
-    ...
-    Step 7 : ADD . /app
-     ---> fae2452e6c35
-    Removing intermediate container 4c93f92a7fd8
-    Step 8 : RUN bundle install --system
-     ---> Running in f851b9cb7d27
-    Using rake 12.0.0
-    Using i18n 0.8.1
-    ...
-    Using web-console 2.3.0
-    Bundle complete! 12 Gemfile dependencies, 56 gems now installed.
-    Bundled gems are installed into /usr/local/bundle.
-     ---> 194830c5c1a8
-    ...
-    Removing intermediate container 67545cd4cd09
-    Step 11 : CMD bin/web
-     ---> Running in b1b26e68d957
-     ---> 8547bb48b21f
-    Removing intermediate container b1b26e68d957
-    Successfully built 8547bb48b21f
-    Docker image tongueroo/demo-ufo:ufo-2017-06-11T22-18-03-a18aa30 built.  Took 33s.
-    $
-
-The docker image tag that is generated contains a useful timestamp and the current HEAD git sha of the project that you are on.
-
-By default when you are running `ufo docker build` directly it does not push the docker image to the registry.  If you would like it to automaticaly push the built image to a registry at the end of the build use the `--push` flag.
-
-    ufo docker build --push
-
-You should see it being pushed at the end:
-
-    Docker image tongueroo/demo-ufo:ufo-2017-06-11T22-22-32-a18aa30 built.  Took 34s.
-    The push refers to a repository [docker.io/tongueroo/demo-ufo]
-    ef375857f165: Pushed
-    4d791d7cde66: Pushed
-    277ff31e79b4: Layer already exists
-    a361a4de05df: Layer already exists
-    ufo-2017-06-11T22-22-32-a18aa30: digest: sha256:c5385a5084e87643bd943eb120e110321c59e8acd30736ba7b5223eb1143baa8 size: 3464
-    Pushed tongueroo/demo-ufo:ufo-2017-06-11T22-22-32-a18aa30 docker image. Took 9s.
-
-Note in order to push the image to a registry you will need to login into the registry.  If you are using DockerHub use the `docker login` command.  If you are using AWS ECR then you can use the `aws ecr get-login` command.
-
-## Docker Build Options
-
-You can specify docker build options with the `UFO_DOCKER_BUILD_OPTIONS` environment variable.  Example:
-
-    $ UFO_DOCKER_BUILD_OPTIONS="--build-arg RAILS_ENV=production" ufo docker build
-    Building docker image with:
-      docker build --build-arg RAILS_ENV=production -t tongueroo/demo-ufo:ufo-2018-05-19T11-52-16-6714713 -f Dockerfile .
-    ...
-    Docker image tongueroo/demo-ufo:ufo-2018-05-19T11-52-16-6714713 built.  Took 2s.
-
-
-## Options
-
-```
-[--push], [--no-push]  
-```
-

data/docs/_reference/ufo-docker-clean.md

@@ -1,44 +0,0 @@
----
-title: ufo docker clean
-reference: true
----
-
-## Usage
-
-    ufo docker clean IMAGE_NAME
-
-## Description
-
-Clean up old images.  Keeps a specified amount.
-
-Ufo comes with a handy command to clean up old images that ufo generates. Ufo only deletes images from the docker daemon and does not remove any images from any registry.  To use it you pass the base portion of the image name to the command.
-
-Say you currently have these images:
-
-    tongueroo/demo-ufo:ufo-2016-10-15T19-29-06-88071f5
-    tongueroo/demo-ufo:ufo-2016-10-16T19-29-06-88071f5
-    tongueroo/demo-ufo:ufo-2016-10-17T19-29-06-88071f5
-    tongueroo/demo-ufo:ufo-2016-10-18T19-29-06-88071f5
-
-To clean them up and keep the 3 more recent:
-
-    $ ufo docker clean tongueroo/demo-ufo
-    Cleaning up docker images...
-    Running: docker rmi tongueroo/demo-ufo:ufo-2016-10-15T19-29-06-88071f5
-
-This will remove tongueroo/demo-ufo:ufo-2016-10-15T19-29-06-88071f5.
-
-By default the clean command keeps the most 3 recent docker images. If you would like to override this setting you can use the `--keep` option. Example:
-
-    ufo docker clean tongueroo/demo-ufo --keep 5
-
-
-## Options
-
-```
-[--keep=N]                 
-                           # Default: 3
-[--tag-prefix=TAG_PREFIX]  
-                           # Default: ufo
-```
-

data/docs/_reference/ufo-docker-compile.md

@@ -1,19 +0,0 @@
----
-title: ufo docker compile
-reference: true
----
-
-## Usage
-
-    ufo docker compile
-
-## Description
-
-Compile Dockerfile.erb
-
-The `ufo docker compile` compiles the Dockerfile using the Dockerfile.erb in the current project folder.  Example:
-
-    ufo docker compile
-
-
-

data/docs/_reference/ufo-docker-help.md

@@ -1,15 +0,0 @@
----
-title: ufo docker help
-reference: true
----
-
-## Usage
-
-    ufo docker help [COMMAND]
-
-## Description
-
-Describe subcommands or one specific subcommand
-
-
-

data/docs/_reference/ufo-docker-name.md

@@ -1,37 +0,0 @@
----
-title: ufo docker name
-reference: true
----
-
-## Usage
-
-    ufo docker name
-
-## Description
-
-Display the full docker image with tag that was last generated.
-
-It is sometimes handy to grab the name of the Docker image that was just generated.  Let's say ou needed the image name so you can feed it into another script that you have. The command `ufo docker name` returns the image of the most recently built Docker image.
-
-## Examples
-
-    ufo docker build # stores the docker image name in the .ufo/data folder
-    ufo docker name  # fetches image name from .ufo/data folder
-
-An example image name would look something like this: `tongueroo/demo-ufo:ufo-2018-02-15T19-29-06-88071f5`
-
-Note, the `.ufo/data` folder is an internal data folder and it's structure can change in future releases.
-
-If you want to generate a brand new name for whatever purpose, you can use the `--generate` flag.  The generate does not write to the `.ufo/data` folder.  It only generates a fresh name to stdout.  If you run it multiple times, it will generate new names.  You can notice this by seeing that the timestamp will always update:
-
-    ufo docker name --generate  # example: tongueroo/demo-ufo:ufo-2018-02-15T10-00-00-88071f5
-    ufo docker name --generate  # example: tongueroo/demo-ufo:ufo-2018-02-15T10-00-08-88071f5
-    ufo docker name --generate  # example: tongueroo/demo-ufo:ufo-2018-02-15T10-00-16-88071f5
-
-
-## Options
-
-```
-[--generate], [--no-generate]  # Generate a name without storing it
-```
-

data/docs/_reference/ufo-docker-push.md

@@ -1,49 +0,0 @@
----
-title: ufo docker push
-reference: true
----
-
-## Usage
-
-    ufo docker push IMAGE
-
-## Description
-
-Push the docker image.
-
-
-The `ufo docker push` command pushes the most recent Docker image built by `ufo docker build` to a registry.  This command pushes a docker image up to the registry.  By default it pushes the last image that was built with `ufo docker build`.  To see what the image name is you can run `ufo docker name`. Example:
-
-    ufo docker build # to build the image
-    ufo docker name  # to see the image name
-    ufo docker push  # push up the registry
-
-You'll see that `ufo docker push` simply shells out and calls `docker push`:
-
-    $ ufo docker push
-    => docker push 123456789.dkr.ecr.us-east-1.amazonaws.com/hi:ufo-2018-02-13T10-51-44-e0cc7be
-    The push refers to a repository [123456789.dkr.ecr.us-east-1.amazonaws.com/hi]
-    399c739c257d: Layer already exists
-    ...
-    Pushed 123456789.dkr.ecr.us-east-1.amazonaws.com/hi:ufo-2018-02-13T10-51-44-e0cc7be docker image. Took 1s.
-    $
-
-You can also push up a custom image by specifying the image name as the first parameter.
-
-    ufo docker push my/image:tag
-
-You could also use the `--push` flag as part of the `ufo docker build` command to achieve the same thing as `ufo docker push`. The `ufo docker push` command might be more intutitive.
-
-    ufo docker build --push # same as above
-
-## Docker Authorization
-
-Note in order to push the image to a registry you will need to login into the registry.  If you are using DockerHub use the `docker login` command.  If you are using AWS ECR then, ufo will automatically try to authorize you and configure your `~/.docker/config.json`.  If can also use `aws ecr get-login` command.
-
-
-## Options
-
-```
-[--push], [--no-push]  
-```
-

data/docs/_reference/ufo-docker.md

@@ -1,38 +0,0 @@
----
-title: ufo docker
-reference: true
----
-
-## Usage
-
-    ufo docker SUBCOMMAND
-
-## Description
-
-docker subcommands
-
-## Examples
-
-    ufo docker base
-    ufo docker build
-    ufo docker name
-    ufo docker push
-
-## Subcommands
-
-* [ufo docker base]({% link _reference/ufo-docker-base.md %}) - Build docker image from `Dockerfile.base` and update current `Dockerfile`.
-* [ufo docker build]({% link _reference/ufo-docker-build.md %}) - Build docker image.
-* [ufo docker clean]({% link _reference/ufo-docker-clean.md %}) - Clean up old images. Keeps a specified amount.
-* [ufo docker compile]({% link _reference/ufo-docker-compile.md %}) - Compile Dockerfile.erb
-* [ufo docker name]({% link _reference/ufo-docker-name.md %}) - Display the full docker image with tag that was last generated.
-* [ufo docker push]({% link _reference/ufo-docker-push.md %}) - Push the docker image.
-
-## Options
-
-```
-[--verbose], [--no-verbose]  
-[--mute], [--no-mute]        
-[--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
-```
-

data/docs/_reference/ufo-init.md

@@ -1,125 +0,0 @@
----
-title: ufo init
-reference: true
----
-
-## Usage
-
-    ufo init --image=IMAGE
-
-## Description
-
-Set up initial ufo files.
-
-The `ufo init` command provides a way to quickly setup a project to be ufo ready. It creates a ufo folder with all the starter supporting files in order to use ufo.  This page demonstrates how to use `ufo init`.  The command requires the `--image` option.  If the `--app` option is not provided, then it is inferred and set as the parent folder name. Example:
-
-    cd demo
-    ufo init --image tongueroo/demo-ufo # same as --app demo
-
-## Examples
-
-For this example we will use [tongueroo/demo-ufo](https://github.com/tongueroo/demo-ufo) which is a small test sinatra app.  Let's run the command in our newly clone project.
-
-    $ git clone https://github.com/tongueroo/demo-ufo.git demo
-    $ cd demo
-    $ ufo init --image=tongueroo/demo-ufo
-    Setting up ufo project...
-          create  .ufo/settings.yml
-          create  .ufo/task_definitions.rb
-          create  .ufo/templates/main.json.erb
-          create  .ufo/variables/base.rb
-          create  .ufo/variables/development.rb
-          create  .ufo/variables/production.rb
-          create  Dockerfile
-          create  bin/deploy
-          append  .gitignore
-    Starter ufo files created.
-
-## More Short Examples
-
-    ufo init --image httpd
-    ufo init --image 123456789012.dkr.ecr.us-west-2.amazonaws.com/myimage
-    ufo init --image tongueroo/demo-ufo --launch-type fargate --execution-role-arn arn:aws:iam::123456789012:role/ecsTaskExecutionRole
-    ufo init --image httpd --vpc-id vpc-123
-
-## Important options
-
-The `app` is that application name that you want to show up on the ECS dashboard.  It is encouraged to have the app name be a single word.  If the option is not provided, the app name is inferred and is the parent folder name.
-
-The `image` is the base portion of image name that will be pushed to the docker registry, ie: DockerHub or AWS ECR.  The image should **not** include the tag since the tag is generated upon a `ufo ship`.  For example:
-
-    tongueroo/demo-ufo => tongueroo/demo-ufo:ufo-2018-02-08T21-04-02-3c86158
-
-The generated `tongueroo/demo-ufo:ufo-2018-02-08T21-04-02-3c86158` image name gets pushed to the docker registry.
-
-The `--vpc-id`, `--ecs-subnets`, and `--elb-subnets` options are optional but very useful. If not specified then ufo will use the default vpc for the network settings like subnets and security groups, which might not be what you want.
-
-## Directory Structure
-
-The standard directory structure of the `.ufo` folder that was created looks like this:
-
-    ufo
-    ├── output
-    ├── settings.yml
-    ├── task_definitions.rb
-    ├── templates
-    │   └── main.json.erb
-    └── variables
-        ├── base.rb
-        ├── production.rb
-        └── development.rb
-
-For a explanation of the folders and files refer to [Structure]({% link _docs/structure.md %}).
-
-## Fargate Support
-
-For ECS Fargate, the ECS task definition structure is a bit different.  To initialize a project to support Fargate use the `--launch-type fargate` option.  You'll be prompted for a execution role arn.  This value gets added to the generated `.ufo/variables/base.rb` and used in the `.ufo/templates/main.json.erb`.
-
-    ufo init --image tongueroo/demo-ufo --app demo --launch-type fargate
-
-You can also generate the init ufo files and bypass the prompt by providing the `--execution-role-arn` option upfront.
-
-    ufo init --image tongueroo/demo-ufo --app demo --launch-type fargate --execution-role-arn arn:aws:iam::123456789012:role/ecsTaskExecutionRole
-
-For more information and a demo of Fargate support, check out the [Quick Start: Fargate Docs]({% link quick-start.md %}).
-
-## Custom Templates
-
-If you would like the `ufo init` command to use your own custom templates, you can achieve this with the `--template` and `--template-mode` options.  Example:
-
-    ufo init --image=tongueroo/demo-ufo --template=tongueroo/ufo-custom-template
-
-This will clone the repo on GitHub into the `~/.ufo/templates/tongueroo/ufo-custom-template` and use that as an additional template source.  The default `--template-mode=additive` mode means that if there's a file in `tongueroo/ufo-custom-template` that exists it will use that in place of the default template files.
-
-If you do not want to use any of the original default template files within the ufo gem at all, you can use the `--template-mode=replace` mode. Replace mode will only use templates from the provided `--template` option.  Example:
-
-    ufo init --image=tongueroo/demo-ufo --template=tongueroo/ufo-custom-template --template-mode=replace
-
-You can also specific the full GitHub url. Example:
-
-    ufo init --image=tongueroo/demo-ufo --template=https://github.com/tongueroo/ufo-custom-template
-
-If you would like to use a local template that is not on GitHub, then created a top-level folder in `~/.ufo/templates` without a subfolder. Example:
-
-    ufo init --image=tongueroo/demo-ufo --template=my-custom # uses ~/.ufo/templates/my-custom
-
-
-## Options
-
-```
-[--force]                        # Bypass overwrite are you sure prompt for existing files.
---image=IMAGE                    # Docker image name without the tag. Example: tongueroo/demo-ufo. Configures ufo/settings.yml
-[--app=APP]                      # App name. Preferably one word. Used in the generated ufo/task_definitions.rb.  If not specified then the app name is inferred as the folder name.
-[--launch-type=LAUNCH_TYPE]      # ec2 or fargate.
-                                 # Default: ec2
-[--template=TEMPLATE]            # Custom template to use.
-[--template-mode=TEMPLATE_MODE]  # Template mode: replace or additive.
-[--vpc-id=VPC_ID]                # Vpc id. For settings/network/default.yml.
-[--ecs-subnets=one two three]    # Subnets for ECS tasks, defaults to --elb-subnets set to. For settings/network/default.yml
-[--elb-subnets=one two three]    # Subnets for ELB. For settings/network/default.yml
-[--verbose], [--no-verbose]      
-[--mute], [--no-mute]            
-[--noop], [--no-noop]            
-[--cluster=CLUSTER]              # Cluster.  Overrides .ufo/settings.yml.
-```
-

data/docs/_reference/ufo-logs.md

@@ -1,40 +0,0 @@
----
-title: ufo logs
-reference: true
----
-
-## Usage
-
-    ufo logs
-
-## Description
-
-Prints out logs
-
-## Examples
-
-    ufo logs demo-web
-
-If you have a current service name set.
-
-    ufo current --service demo-web
-    ufo logs # follow by default
-    ufo logs --no-follow
-    ufo logs --format detailed # to show stream too
-
-
-## Options
-
-```
-[--follow], [--no-follow]          #  Whether to continuously poll for new logs. To exit from this mode, use Control-C.
-                                   # Default: true
-[--since=SINCE]                    # From what time to begin displaying logs.  By default, logs will be displayed starting from 1 minutes in the past. The value provided can be an ISO 8601 timestamp or a relative time.
-[--format=FORMAT]                  # The format to display the logs. IE: detailed or short.  With detailed, the log stream name is also shown.
-                                   # Default: detailed
-[--filter-pattern=FILTER_PATTERN]  # The filter pattern to use. If not provided, all the events are matched
-[--verbose], [--no-verbose]        
-[--mute], [--no-mute]              
-[--noop], [--no-noop]              
-[--cluster=CLUSTER]                # Cluster.  Overrides .ufo/settings.yml.
-```
-

data/docs/_reference/ufo-network-help.md

@@ -1,15 +0,0 @@
----
-title: ufo network help
-reference: true
----
-
-## Usage
-
-    ufo network help [COMMAND]
-
-## Description
-
-Describe subcommands or one specific subcommand
-
-
-

data/docs/_reference/ufo-network-init.md

@@ -1,39 +0,0 @@
----
-title: ufo network init
-reference: true
----
-
-## Usage
-
-    ufo network init
-
-## Description
-
-Creates network starter settings file.
-
-## Examples
-
-    ufo network init # will use default vpc and subnets
-    ufo network init --vpc-id vpc-123
-    ufo network init --vpc-id vpc-123 --subnets subnet-aaa subnet-bbb
-
-If the `--vpc-id` option is set and the `--subnets` is not, then ufo generates files with all the associated subnets from the specified vpc id.
-
-You can also specify name of the settings file to create with the `--filename` option.  Example.
-
-    ufo network init --vpc-id vpc-123 --filename dev
-
-The above command creates a `.ufo/settings/network/dev.yml` file.  You might want to then update your `.ufo/settings.yml` file and update the `network_profile` config to reference it.
-
-
-## Options
-
-```
-[--force]                      # Bypass overwrite are you sure prompt for existing files.
-[--ecs-subnets=one two three]  # ECS Subnets
-[--elb-subnets=one two three]  # ELB Subnets
-[--vpc-id=VPC_ID]              # Vpc id
-[--filename=FILENAME]          # Name of the settings file to create w/o extension.
-                               # Default: default
-```
-

data/docs/_reference/ufo-network.md

@@ -1,26 +0,0 @@
----
-title: ufo network
-reference: true
----
-
-## Usage
-
-    ufo network SUBCOMMAND
-
-## Description
-
-network subcommands
-
-## Subcommands
-
-* [ufo network init]({% link _reference/ufo-network-init.md %}) - Creates network starter settings file.
-
-## Options
-
-```
-[--verbose], [--no-verbose]  
-[--mute], [--no-mute]        
-[--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
-```
-

data/docs/_reference/ufo-ps.md

@@ -1,56 +0,0 @@
----
-title: ufo ps
-reference: true
----
-
-## Usage
-
-    ufo ps SERVICE
-
-## Description
-
-Show process info on ECS service.
-
-## Examples
-
-    $ ufo ps
-    => Service: demo-web
-       Service name: development-demo-web-Ecs-7GAUAXH5F56M
-       Status: ACTIVE
-       Running count: 2
-       Desired count: 2
-       Launch type: FARGATE
-       Task definition: demo-web:85
-       Elb: develop-Elb-1M74CLRS2G0Z4-686742146.us-east-1.elb.amazonaws.com
-    +----------+------+-------------+----------------+---------+-------+
-    |    Id    | Name |   Release   |    Started     | Status  | Notes |
-    +----------+------+-------------+----------------+---------+-------+
-    | f590ee5e | web  | demo-web:85 | 47 minutes ago | RUNNING |       |
-    | fb60ba9f | web  | demo-web:85 | 45 minutes ago | RUNNING |       |
-    +----------+------+-------------+----------------+---------+-------+
-
-Skip the summary info:
-
-    $ ufo ps --no-summary
-    +----------+------+-------------+----------------+---------+-------+
-    |    Id    | Name |   Release   |    Started     | Status  | Notes |
-    +----------+------+-------------+----------------+---------+-------+
-    | f590ee5e | web  | demo-web:85 | 48 minutes ago | RUNNING |       |
-    | fb60ba9f | web  | demo-web:85 | 45 minutes ago | RUNNING |       |
-    +----------+------+-------------+----------------+---------+-------+
-
-
-## Options
-
-```
-[--summary], [--no-summary]  # Display summary header info.
-                             # Default: true
-[--extra], [--no-extra]      # Display extra debugging columns.
-[--status=STATUS]            # Status filter: all, pending, stopped, running.
-                             # Default: all
-[--verbose], [--no-verbose]  
-[--mute], [--no-mute]        
-[--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
-```
-