App Templates - Nuon documentation

An App Template is a series of TOML files that describe how your app is structured and what it depends on. Each install is one deployment of an App Template. Most teams keep one template per cloud or architecture, such as AWS and Azure.

What’s in a template

A template is a directory of TOML files in your own git repo. The configuration reference covers each file.

my-app/
├── metadata.toml   # name and README
├── inputs.toml     # customer values
├── secrets.toml    # customer credentials
├── policies.toml   # policy checks
├── components/     # your product
├── actions/        # scripts
├── runbooks/       # procedures
│
│   # BYOC management infra
├── stack.toml      # install stack
├── runner.toml     # runner settings
└── sandbox.toml    # VPC, cluster

Metadata: the template’s name and README.
Inputs: values each customer sets, such as region.
Secrets: credentials each customer supplies.
Policies: checks that run before a build or deploy.
Components: your Helm charts, Terraform modules, manifests, and images.
Actions: scripts you run against installs.
Runbooks: multi-step procedures for installs.

BYOC management infra:

Stack: what the customer applies first, such as the network and permissions.
Runner: settings for the runner in each customer’s account.
Sandbox: base infrastructure, such as a VPC and cluster.

Change your App Template any time. Push to git, and an app branch rolls the change out to your installs.

​What’s in a template

What’s in a template