ufo 3.5.7 → 4.0.0

data/lib/ufo/destroy.rb

@@ -1,57 +1,26 @@
 module Ufo
-  class Destroy
-    include Util
-    include AwsService
-
-    def initialize(service, options={})
-      @service = service
-      @options = options
-      @cluster = @options[:cluster] || default_cluster
-    end
-
+  class Destroy < Base
     def bye
       unless are_you_sure?
         puts "Phew, that was close"
-        exit
+        return
       end
 
-      clusters = ecs.describe_clusters(clusters: [@cluster]).clusters
-      if clusters.size < 1
-        puts "The #{@cluster} cluster does not exist so there can be no service on that cluster to delete."
-        exit
-      end
-
-      services = ecs.describe_services(cluster: @cluster, services: [@service]).services
-      service = services.first
-      if service.nil?
-        puts "Unable to find #{@service} service to delete it."
-        exit
-      end
-      if service.status != "ACTIVE"
-        puts "The #{@service} service is not ACTIVE so no need to delete it."
+      stack = find_stack(@stack_name)
+      unless stack
+        puts "Stack #{@stack_name} does not exit"
         exit
       end
 
-      # changes desired size to 0
-      ecs.update_service(
-        desired_count: 0,
-        cluster: @cluster,
-        service: @service
-      )
-      # Cannot find all tasks scoped to a service.  Only scoped to a cluster.
-      # So will not try to stop the tasks.
-      # ask to stop them
-      #
-      resp = ecs.delete_service(
-        cluster: @cluster,
-        service: @service
-      )
-      puts "#{@service} service has been scaled down to 0 and destroyed." unless @options[:mute]
+      cloudformation.delete_stack(stack_name: @stack_name)
+      puts "Deleting CloudFormation stack with ECS resources: #{@stack_name}."
+      return unless @options[:wait]
+      status.wait
     end
 
     def are_you_sure?
       return true if @options[:sure]
-      puts "You are about to destroy #{@service.colorize(:green)} service on the #{@cluster.colorize(:green)} cluster."
+      puts "You are about to destroy #{@pretty_service_name.colorize(:green)} service on the #{@cluster.colorize(:green)} cluster."
       print "Are you sure you want to do this? (y/n) "
       answer = $stdin.gets.strip
       answer =~ /^y/

data/lib/ufo/docker/builder.rb

@@ -41,7 +41,8 @@ class Ufo::Docker
       end
 
       took = Time.now - start_time
-      say "Docker image #{full_image_name} built.  " + "Took #{pretty_time(took)}.".green
+      say "Docker image #{full_image_name} built.  "
+      say "Docker build took #{pretty_time(took)}.".green
     end
 
     def build_options
@@ -89,15 +90,15 @@ class Ufo::Docker
 
     # full_image - does not include the tag
     def image_name
-      settings["image"]
+      settings[:image]
     end
 
     # full_image - Includes the tag. Examples:
     #   123456789.dkr.ecr.us-west-2.amazonaws.com/myapp:ufo-2018-04-20T09-29-08-b7d51df
-    #   tongueroo/hi:ufo-2018-04-20T09-29-08-b7d51df
+    #   tongueroo/demo-ufo:ufo-2018-04-20T09-29-08-b7d51df
     def full_image_name
       return generate_name if @options[:generate]
-      return "tongueroo/hi:ufo-12345678" if ENV['TEST']
+      return "tongueroo/demo-ufo:ufo-12345678" if ENV['TEST']
 
       unless File.exist?(docker_name_path)
         puts "Unable to find #{docker_name_path} which contains the last docker image name that was used as a part of `ufo docker build`.  Please run `ufo docker build` first."

data/lib/ufo/docker/cleaner.rb

@@ -7,7 +7,7 @@ module Ufo
       # Example: 123456789.dkr.ecr.us-east-1.amazonaws.com/image
       @docker_image_name = docker_image_name
       @options = options
-      @keep = options[:keep] || settings["clean_keep"] || 3
+      @keep = options[:keep] || settings[:clean_keep] || 3
       @tag_prefix = options[:tag_prefix] || "ufo"
     end
 

data/lib/ufo/docker/pusher.rb

@@ -29,7 +29,7 @@ class Ufo::Docker
         end
       end
       took = Time.now - start_time
-      message << " Took #{pretty_time(took)}.".green
+      message << "\nDocker push took #{pretty_time(took)}.".green
       puts message unless @options[:mute]
     end
 
@@ -45,7 +45,7 @@ class Ufo::Docker
 
     # full_image - does not include the tag
     def image_name
-      settings["image"]
+      settings[:image]
     end
   end
 end

data/lib/ufo/ecr/cleaner.rb

@@ -13,7 +13,7 @@ module Ufo
       # Example: 123456789.dkr.ecr.us-east-1.amazonaws.com/image
       @docker_image_name = docker_image_name
       @options = options
-      @keep = options[:ecr_keep] || settings["ecr_keep"]
+      @keep = options[:ecr_keep] || settings[:ecr_keep]
       @tag_prefix = options[:tag_prefix] || "ufo"
     end
 

data/lib/ufo/help/apps.md

@@ -0,0 +1,12 @@
+This command lists ECS services for an ECS cluster. It includes ECS services that were not created by ufo also.  A `Ufo?` column value of `yes` indicates that the ECS service was created by ufo version 4 and above.  If the service was created with ufo version 3 and below then it will show up as `no`.
+
+## Examples
+
+    $ ufo apps
+    Listing ECS services in the development cluster.
+    +--------------------------------------------------+-----------------+---------+-------------+------+
+    |                   Service Name                   | Task Definition | Running | Launch type | Ufo? |
+    +--------------------------------------------------+-----------------+---------+-------------+------+
+    | development-demo-web-Ecs-7GAUAXH5F56M (demo-web) | demo-web:85     | 2       | FARGATE     | yes  |
+    +--------------------------------------------------+-----------------+---------+-------------+------+
+    $

data/lib/ufo/help/balancer.md

@@ -0,0 +1,3 @@
+## Examples
+
+  ufo network init

data/lib/ufo/help/current.md

@@ -0,0 +1,65 @@
+Sets a current service to remember so you do not have to provide the service name all the time.  This shortens the commands
+
+    ufo ship demo-web # before
+    ufo current --service demo-web
+    ufo ship # after
+
+The state information is written to `.ufo/current`.
+
+## Examples
+
+### summary
+
+    ufo current --service demo-web --env-extra 1
+    ufo current --service demo-web --env-extra 1 --services demo-web demo-worker
+    ufo current --service demo-web --env-extra ''
+    ufo current --service demo-web
+    ufo current --env-extra '1'
+
+### service
+
+To set current service:
+
+    ufo current --service demo-web
+    ufo current --service demo-worker
+    ufo current --service demo-web
+
+To view current service, run `ufo current` without any arguments.
+
+    $ ufo current
+    Current service: demo-web
+
+To remove current service:
+
+    ufo current --service ''
+
+### env-extra
+
+To also set a current `UFO_ENV_EXTRA`.
+
+    ufo current --env-extra 1
+
+The extra env setting will be reflected:
+
+    $ ufo current
+    Current service: demo-web
+    Current env_extra: 1
+
+The `UFO_ENV_EXTRA` variable takes higher precedence than the current setting in the saved file.
+
+To unset:
+
+    ufo current --env-extra ''
+
+### services
+
+The ufo ships command builds one docker image and deploys it to multiple ECS services. You can also have ufo remember what services to use with the current command.
+
+    ufo current --services demo-web demo-worker
+    ufo ships # will depoy to both demo-web and demo-worker
+
+### rm all
+
+To remove all current settings use the `--rm` option.
+
+    ufo current --rm

data/lib/ufo/help/deploy.md

@@ -1,15 +1,15 @@
-It is useful to sometimes deploy only the task definition without re-building it.  Say for example, you are debugging the task definition and just want to directly edit the `.ufo/output/hi-web.json` definition. You can accomplish this with the `ufo deploy` command.  The `ufo deploy` command will deploy the task definition in `.ufo/output` unmodified.  Example:
+It is useful to sometimes deploy only the task definition without re-building it.  Say for example, you are debugging the task definition and just want to directly edit the `.ufo/output/demo-web.json` definition. You can accomplish this with the `ufo deploy` command.  The `ufo deploy` command will deploy the task definition in `.ufo/output` unmodified.  Example:
 
-    ufo deploy hi-web
+    ufo deploy demo-web
 
 The above command does the following:
 
-1. register the `.ufo/output/hi-web.json` task definition to ECS untouched.
+1. register the `.ufo/output/demo-web.json` task definition to ECS untouched.
 2. deploys it to ECS by updating the service
 
 ### ufo tasks build
 
-To regenerate a `.ufo/output/hi-web.json` definition:
+To regenerate a `.ufo/output/demo-web.json` definition:
 
     ufo tasks build
 

data/lib/ufo/help/destroy.md

@@ -1,9 +1,9 @@
 ## Examples
 
-Ufo provides a quick way to destroy an ECS service. To destroy an ECS service, you must make sure that the desired number of tasks is first set to 0. It is easy to forget to do this and waste time. So as part of destroying the service ufo will scale the ECS service down to 0 automatically first and then destroys the service.  Ufo also prompts you before destroying the service.
+Ufo provides a quick way to destroy an ECS service. This is effectively the same thing as deleting the CloudFormation stack.
 
-    ufo destroy hi-web
+    ufo destroy demo-web
 
 If you would like to bypass the prompt, you can use the `--sure` option.
 
-    ufo destroy hi-web --sure
+    ufo destroy demo-web --sure

data/lib/ufo/help/docker.md

@@ -1,4 +1,6 @@
 ## Examples
 
+  ufo docker base
   ufo docker build
-  ufo docker tag
+  ufo docker name
+  ufo docker push

data/lib/ufo/help/docker/base.md

@@ -6,7 +6,7 @@ updates the FROM `Dockerfile` image with the generated image from `Dockerfile.ba
   ufo docker base
   ufo docker base --no-push # do not push the image to the registry
 
-Docker image `tongueroo/hi:base-2016-10-21T15-50-57-88071f5` built.
+Docker image `tongueroo/demo-ufo:base-2016-10-21T15-50-57-88071f5` built.
 
 ## Concept
 
@@ -18,22 +18,22 @@ There are pros and cons of using this approach.  Remember there are 2 hard probl
 
 ## Demo
 
-To demonstrate this command, there's a `docker-cache` branch in the [tongueroo/hi](https://github.com/tongueroo/hi/tree/docker-cache) repo.
+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/hi:base-2017-06-12T14-36-44-2af505e -f Dockerfile.base .
+      docker build -t tongueroo/demo-ufo:base-2017-06-12T14-36-44-2af505e -f Dockerfile.base .
       ...
-    Pushed tongueroo/hi:base-2017-06-12T14-36-44-2af505e docker image. Took 28s.
+    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/hi:base-2017-06-12T14-36-44-2af505e
+      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/hi:base-2017-06-12T14-36-44-2af505e -f Dockerfile.base .
+    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/hi: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.
+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.
 
 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.

data/lib/ufo/help/docker/build.md

@@ -1,16 +1,16 @@
-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/hi](https://github.com/tongueroo/hi) project and it's Dockerfile for demonstration.  Example:
+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/hi:ufo-2017-06-11T22-18-03-a18aa30 -f Dockerfile .
+    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/hi:ufo-2017-06-11T22-18-03-a18aa30 -f Dockerfile .
+      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
@@ -37,7 +37,7 @@ You should see similar output (some of the output has been truncated for concise
      ---> 8547bb48b21f
     Removing intermediate container b1b26e68d957
     Successfully built 8547bb48b21f
-    Docker image tongueroo/hi:ufo-2017-06-11T22-18-03-a18aa30 built.  Took 33s.
+    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.
@@ -48,14 +48,14 @@ By default when you are running `ufo docker build` directly it does not push the
 
 You should see it being pushed at the end:
 
-    Docker image tongueroo/hi:ufo-2017-06-11T22-22-32-a18aa30 built.  Took 34s.
-    The push refers to a repository [docker.io/tongueroo/hi]
+    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/hi:ufo-2017-06-11T22-22-32-a18aa30 docker image. Took 9s.
+    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.
 
@@ -65,6 +65,6 @@ You can specify docker build options with the `UFO_DOCKER_BUILD_OPTIONS` environ
 
     $ 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/hi:ufo-2018-05-19T11-52-16-6714713 -f Dockerfile .
+      docker build --build-arg RAILS_ENV=production -t tongueroo/demo-ufo:ufo-2018-05-19T11-52-16-6714713 -f Dockerfile .
     ...
-    Docker image tongueroo/hi:ufo-2018-05-19T11-52-16-6714713 built.  Took 2s.
+    Docker image tongueroo/demo-ufo:ufo-2018-05-19T11-52-16-6714713 built.  Took 2s.

data/lib/ufo/help/docker/clean.md

@@ -2,19 +2,19 @@ Ufo comes with a handy command to clean up old images that ufo generates. Ufo on
 
 Say you currently have these images:
 
-    tongueroo/hi:ufo-2016-10-15T19-29-06-88071f5
-    tongueroo/hi:ufo-2016-10-16T19-29-06-88071f5
-    tongueroo/hi:ufo-2016-10-17T19-29-06-88071f5
-    tongueroo/hi:ufo-2016-10-18T19-29-06-88071f5
+    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/hi
+    $ ufo docker clean tongueroo/demo-ufo
     Cleaning up docker images...
-    Running: docker rmi tongueroo/hi:ufo-2016-10-15T19-29-06-88071f5
+    Running: docker rmi tongueroo/demo-ufo:ufo-2016-10-15T19-29-06-88071f5
 
-This will remove tongueroo/hi: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/hi --keep 5
+    ufo docker clean tongueroo/demo-ufo --keep 5

data/lib/ufo/help/docker/name.md

@@ -5,12 +5,12 @@ It is sometimes handy to grab the name of the Docker image that was just generat
     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/hi:ufo-2018-02-15T19-29-06-88071f5`
+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/hi:ufo-2018-02-15T10-00-00-88071f5
-    ufo docker name --generate  # example: tongueroo/hi:ufo-2018-02-15T10-00-08-88071f5
-    ufo docker name --generate  # example: tongueroo/hi:ufo-2018-02-15T10-00-16-88071f5
+    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

data/lib/ufo/help/help.md

@@ -0,0 +1,5 @@
+Displays process information about the service.
+
+## Examples
+
+    $ ufo ps demo-web

data/lib/ufo/help/init.md

@@ -1,12 +1,15 @@
-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 these options: `--app` and `--image`.
+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/hi](https://github.com/tongueroo/hi) which is a small test sinatra app.  Let's run the command in our newly clone project.
+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/hi.git
-    $ cd hi
-    $ ufo init --app=hi --image=tongueroo/hi
+    $ git clone https://github.com/tongueroo/demo-ufo.git
+    $ cd demo-ufo
+    $ ufo init --app=demo --image=tongueroo/demo-ufo
     Setting up ufo project...
           create  .ufo/settings.yml
           create  .ufo/task_definitions.rb
@@ -23,17 +26,20 @@ For this example we will use [tongueroo/hi](https://github.com/tongueroo/hi) whi
 
     ufo init --image httpd --app demo
     ufo init --image 123456789012.dkr.ecr.us-west-2.amazonaws.com/myimage --app demo
-    ufo init --image tongueroo/hi --app hi --launch-type fargate --execution-role-arn arn:aws:iam::536766270177:role/ecsTaskExecutionRole
+    ufo init --image tongueroo/demo-ufo --app demo --launch-type fargate --execution-role-arn arn:aws:iam::123456789012:role/ecsTaskExecutionRole
+    ufo init --image httpd --app demo --vpc-id vpc-123
 
-## Options: app and image
+## 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.
+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/hi => tongueroo/hi:ufo-2018-02-08T21-04-02-3c86158
+    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 generated `tongueroo/hi:ufo-2018-02-08T21-04-02-3c86158` image name gets pushed to the docker registry.
+The `--vpc-id` option is 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
 
@@ -56,30 +62,32 @@ For a explanation of the folders and files refer to [Structure]({% link _docs/st
 
 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/hi --app hi --force --launch-type fargate
+    ufo init --image tongueroo/demo-ufo --app demo --force --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/hi --app hi --force --launch-type fargate --execution-role-arn arn:aws:iam::536766270177:role/ecsTaskExecutionRole
+    ufo init --image tongueroo/demo-ufo --app demo --force --launch-type fargate --execution-role-arn arn:aws:iam::123456789012:role/ecsTaskExecutionRole
 
 Important: You will need to adjust adjust the generated `.ufo/params.yml` and set the subnet and security_group values which are required for Fargate.
 
+For more information and a demo of Fargate support, check out the [Fargate Docs]({% link _docs/fargate.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 --app=hi --image=tongueroo/hi --template=tongueroo/ufo-custom-template
+    ufo init --app=demo --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 --app=hi --image=tongueroo/hi --template=tongueroo/ufo-custom-template --template-mode=replace
+    ufo init --app=demo --image=tongueroo/demo-ufo --template=tongueroo/ufo-custom-template --template-mode=replace
 
 You can also specific the full GitHub url. Example:
 
-    ufo init --app=hi --image=tongueroo/hi --template=https://github.com/tongueroo/ufo-custom-template
+    ufo init --app=demo --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 --app=hi --image=tongueroo/hi --template=my-custom # uses ~/.ufo/templates/my-custom
+    ufo init --app=demo --image=tongueroo/demo-ufo --template=my-custom # uses ~/.ufo/templates/my-custom