ufo 3.5.7 → 4.0.0

data/docs/_reference/ufo-deploy.md

@@ -11,18 +11,18 @@ reference: true
 
 Deploy task definition to ECS service without re-building the definition.
 
-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
 
@@ -42,18 +42,19 @@ The `ufo ships`, `ufo ship`, `ufo deploy` command support the same options. The
 ## Options
 
 ```
-[--task=TASK]                                        # ECS task name, to override the task name convention.
-[--target-group=TARGET_GROUP]                        # ELB Target Group ARN.
-[--target-group-prompt], [--no-target-group-prompt]  # Enable Target Group ARN prompt
-                                                     # Default: true
-[--wait], [--no-wait]                                # Wait for deployment to complete
-[--pretty], [--no-pretty]                            # Pretty format the json for the task definitions
-                                                     # Default: true
-[--stop-old-tasks], [--no-stop-old-tasks]            # Stop old tasks after waiting for deploying to complete
-[--ecr-keep=N]                                       # ECR specific cleanup of old images.  Specifies how many images to keep.  Only runs if the images are ECR images. Defaults keeps all images.
-[--verbose], [--no-verbose]                          
-[--mute], [--no-mute]                                
-[--noop], [--no-noop]                                
-[--cluster=CLUSTER]                                  # Cluster.  Overrides ufo/settings.yml.
+[--ecr-keep=N]                             # ECR specific cleanup of old images.  Specifies how many images to keep.  Only runs if the images are ECR images. Defaults keeps all images.
+[--elb=ELB]                                # Decides to create elb, not create elb or use existing target group.
+[--elb-eip-ids=one two three]              # EIP Allocation ids to use for network load balancer.
+[--elb-type=ELB_TYPE]                      # ELB type: application or network. Keep current deployed elb type when not specified.
+[--pretty], [--no-pretty]                  # Pretty format the json for the task definitions
+                                           # Default: true
+[--stop-old-tasks], [--no-stop-old-tasks]  # Stop old tasks as part of deployment to speed it up
+[--task=TASK]                              # ECS task name, to override the task name convention.
+[--wait], [--no-wait]                      # Wait for deployment to complete
+                                           # Default: true
+[--verbose], [--no-verbose]                
+[--mute], [--no-mute]                      
+[--noop], [--no-noop]                      
+[--cluster=CLUSTER]                        # Cluster.  Overrides .ufo/settings.yml.
 ```
 

data/docs/_reference/ufo-destroy.md

@@ -13,22 +13,24 @@ Destroy the ECS service.
 
 ## 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
 
 
 ## Options
 
 ```
 [--sure], [--no-sure]        # By pass are you sure prompt.
+[--wait], [--no-wait]        # Wait for completion
+                             # Default: true
 [--verbose], [--no-verbose]  
 [--mute], [--no-mute]        
 [--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides ufo/settings.yml.
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
 ```
 

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

@@ -19,7 +19,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
 
@@ -31,23 +31,23 @@ 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/docs/_reference/ufo-docker-build.md

@@ -11,19 +11,19 @@ reference: true
 
 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/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
@@ -50,7 +50,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.
@@ -61,14 +61,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.
 
@@ -78,9 +78,9 @@ 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.
 
 
 ## Options

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

@@ -15,22 +15,22 @@ 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
 
 
 ## Options

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

@@ -18,15 +18,15 @@ 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
 
 
 ## Options

data/docs/_reference/ufo-docker.md

@@ -13,8 +13,10 @@ docker subcommands
 
 ## Examples
 
+    ufo docker base
     ufo docker build
-    ufo docker tag
+    ufo docker name
+    ufo docker push
 
 ## Subcommands
 
@@ -30,6 +32,6 @@ docker subcommands
 [--verbose], [--no-verbose]  
 [--mute], [--no-mute]        
 [--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides ufo/settings.yml.
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
 ```
 

data/docs/_reference/ufo-init.md

@@ -5,21 +5,24 @@ reference: true
 
 ## Usage
 
-    ufo new --app=APP --image=IMAGE
+    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 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
@@ -36,17 +39,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
 
@@ -69,49 +75,54 @@ 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
 
 
 ## Options
 
 ```
 [--force]                                  # Bypass overwrite are you sure prompt for existing files.
---image=IMAGE                              # Docker image name without the tag. Example: tongueroo/hi. Configures ufo/settings.yml
---app=APP                                  # App name. Preferably one word. Used in the generated ufo/task_definitions.rb.
+--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
 [--execution-role-arn=EXECUTION_ROLE_ARN]  # execution role arn used by tasks, required for fargate.
 [--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.
+[--cluster=CLUSTER]                        # Cluster.  Overrides .ufo/settings.yml.
 ```
 

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

@@ -0,0 +1,15 @@
+---
+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

@@ -0,0 +1,38 @@
+---
+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.
+[--subnets=one two three]  # 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

@@ -0,0 +1,26 @@
+---
+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.
+```
+