Skip to main content
The CLI is the primary interface for managing apps. To see all available commands, run nuon apps --help.

Creating an App

Create a directory for your app config files in a GitHub repository, then create the app:
The directory can have any name. The app branch’s directory setting tells Nuon where to find it. nuon apps create also selects the new app.

Adding the Required Files

A valid app needs these three files. The sandbox and runner are part of Nuon’s install infrastructure.
metadata.toml
sandbox.toml
runner.toml
Then add a component for each Helm chart, Terraform module, or container image you deploy. You can point a component at an existing chart or module without rewriting it. The configuration reference covers every file and field. An app you install into a customer account also defines the provision, deprovision, and maintenance roles in its permissions config. See Operation Roles.

Validating the Config

Check the directory before you push:
It looks up the app by the directory’s name, so it works when the directory and the app share a name.

Selecting an App

Select an app to make it the default for all app commands, avoiding the need to pass -a each time:

Common Commands

Shipping the Config

App config ships through an app branch. Commit the config to your repo, add a branch file, and sync it once:
After that, each push to the tracked git branch builds what changed and rolls it out to your installs. See App Branches for the branch file, and Multiple App Configurations to run more than one.