​
What is an Install?

When an Install is created, a Runner is initially created as a VM in the customer’s cloud and is responsible for deploying the Sandbox, Components, and Actions in your App in the correct order defined in the App Config.

​
Install Lifecycle

When an Install is created, the following Components are provisioned:

  • Runner - the Nuon managed Runner that manages the Install.
  • Sandbox - the base infrastructure for networking and compute.
  • Components - the parts of your App.
  • Actions - any operational tasks that can be run in the Install.

When an Install is deleted, each Component will be deleted in reverse order, according to its dependencies, and then the Sandbox is destroyed. The Runner is then deleted by deleting the configuration that was used to create it. e.g., deleting the AWS CloudFormation stack.

​
Install Management

The primary and recommended way to create and manage Installs is through the Dashboard. The Dashboard outputs the AWS CloudFormation stack link to create the Runner and kick off the Install process.

The cli exposes many operational commands to manage an Install.

To see all available commands, run: nuon installs --help.

​
Pinning an Install

You can pin an Install, which will set it’s ID as a default argument to all Install commands. This is helpful to avoid having to pass -i to each command.

nuon installs select

Each example below assumes you have run nuon installs select first.

To show the currently pinned Install:

nuon installs current

​
Install Management Commands

Commands for creating, deleting and viewing Installs.

Create an Install - create an Install for an AWS application, passing in one or more Inputs.

Creating Azure Installs is currently only supported using an installer, or our API.

nuon installs create  \
  --name=install \
  --region=us-east-1 \
  --role=iam-role

Delete an Install - Delete an Install

nuon installs delete

List all Installs - list an Install

nuon installs list

Get an Install - get an Install

nuon installs get

​
Install Sandbox Commands

Commands for working with an Install’s Sandbox.

Show Sandbox updates - show all updates to an Install’s Sandbox.

nuon installs sandbox-runs

Show Sandbox run logs - show logs for a specific Sandbox run.

nuon installs sandbox-run-logs -r <run-id>

Reprovision a Sandbox - reprovision the Sandbox with the latest configured Sandbox version for an App.

nuon installs reprovision

Deprovision a Sandbox - Deprovision a Sandbox.

nuon installs deprovision

​
Install Components

Each Component is deployed to an Install when it is first created. When a Component is created after an Install has been provisioned, it will automatically be deployed to it upon the first release.

The Nuon CLI provides the following commands to manage install Components:

Each example here assumes you have run nuon installs select first.

Show Deploys - show deploys for an Install.

nuon installs list-deploys

Deploy Logs - print logs for a deploy.

nuon installs deploy-logs -d <deploy-id>

Deploy Plan - print a deploy plan for an install.

nuon installs print-deploy-plan -d <deploy-id>

​
Deploying to a specific Install

While iterating on your App’s config, it can be helpful to deploy to a single Install, you can do this by creating a release and targeting a single Install id.

nuon releases create -i <install-id> -c <component>