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

​
Creating an App

Create a directory for your app config files, then create the app:
The app name should match the directory name.

​
Pinning an App

Pin an app to set its ID as the default for all app commands, avoiding the need to pass -a each time:
Examples below assume you have run nuon apps select first.

​
Common Commands

​
Syncing Configuration

Sync uploads your TOML config files to the Nuon control plane and triggers builds for any changed components:
If component TOML files or related files (e.g., Helm values.yaml) have changed, a new build is triggered during sync. If component source files have changed, push those changes to your git repo first, then build the component manually using the dashboard or CLI.

​
Viewing Configuration

The output of runner-config, sandbox-config, and input-config is JSON. Pipe through jq or python -m json.tool for readability.

​
Metadata

Add metadata to your app via a metadata.toml file in the app root directory. This metadata is used in installers and the dashboard:
metadata.toml
The readme field points to a Markdown file rendered in the dashboard for each install. See the Using READMEs guide for details.

​
Label colors

Give labels custom colors in the dashboard with a label_colors table in metadata.toml. Keys are label key names; values are hex color codes:
metadata.toml
The colors apply wherever those label keys appear in the dashboard — on apps, installs, and components. You can also set label colors directly in the dashboard; either source can be updated later, and a sync will reconcile the values from your config.