Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nuon.co/llms.txt

Use this file to discover all available pages before exploring further.

When you ship an app to customers through Nuon, you create one install per customer. This page covers configuring those installs, labeling them so they’re easy to identify, and monitoring their workflows once they’re running.

​
Install Configs

If you create installs at scale — for example, one per customer in an automated onboarding flow — you can generate install configs programmatically instead of authoring them by hand. Install configs are defined by a JSON Schema that lists every field, its type, and its validation rules. Feed the schema to a code generator, validator, or template engine and produce install configs from your own data. Apply a generated config with the Nuon CLI: 
nuon installs sync --file <your-install>.toml --app-id <your-app-id> --yes
For the full property list, see the Install configuration reference.

​
Labeling installs

Installs support arbitrary key/value labels set via the labels field in the install config. Labels are useful for tagging installs with metadata like environment, region, or version, and they’re surfaced in the dashboard alongside the install.
install.toml
name = "customer-acme"

[labels]
env = "production"
region = "us-east-1"
tier = "enterprise"
See Label badges for how labels render in install READMEs.

​
Monitoring in-progress workflows

Once an install kicks off a deploy — or any other workflow — you can monitor progress from the dashboard, via outbound webhooks, or via Slack notifications. Connect your workspace to get real-time deploy notifications — see the Slack integration guide. For programmatic integrations, webhooks deliver the same workflow lifecycle events as CloudEvents over HTTP.