> ## 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.

# Updates and Operations

> Ship changes across your installs with change controls, then keep each install healthy.

Every change to an install runs as a [workflow](https://docs.nuon.co/concepts/workflows.md) with a plan you can review, checked against your
[policies](https://docs.nuon.co/concepts/policies.md).

## Push updates

Because App Templates live in git, an update is a push.

* **Roll out across installs.** A push to the tracked branch builds what changed, then plans and deploys it one
  [install group](https://docs.nuon.co/concepts/app-branches.md#install-groups) at a time.
* **Review before it ships.** Each install group waits for you to approve its Terraform plan or Helm diff.
* **Approve automatically.** [Auto-approve plans](https://docs.nuon.co/concepts/workflows.md#workflow-approvals) on an install, or let a group
  approve itself when every [policy](https://docs.nuon.co/concepts/policies.md) check passes.
* **Change one customer.** Edit that install's [config](https://docs.nuon.co/guides/install-configs.md), or
  [roll it back](https://docs.nuon.co/guides/rollback-install-config.md) to an earlier version.

## Migrations, runbooks, and debugging

For work that isn't a config change:

* **[Runbooks](https://docs.nuon.co/guides/runbooks.md)** chain deploys and actions into one procedure, such as a database migration or a
  recovery.
* **[Actions](https://docs.nuon.co/concepts/actions.md)** run scripts by hand, on a schedule, or around a deploy, and can fix what monitoring
  finds.
* **[Workflows](https://docs.nuon.co/concepts/workflows.md)** record every run's steps and logs, so you can see what ran, when, and against
  which install.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.