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.
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.
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.
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.
Copy
Ask AI
nuon installs select
Each example below assumes you have run nuon installs select first.
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.
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.