Container scripts

A CT script belongs in ct/<slug>.sh. It defines the application defaults and starts the Core lifecycle; it does not implement host detection, the wizard, container creation, or the in-container bootstrap.

The exact same lifecycle is used on Proxmox VE and Incus. Core detects the host and loads the appropriate backend. Keep a CT script platform-neutral unless the application itself is genuinely platform-specific.

Required flowCopy Anchor Link

1. Load core/build.func using the local-first bootstrap.
2. Declare APP and var_* application defaults.
3. Initialise Core with header_info, variables, color, and catch_errors.
4. Optionally provide update_script for application update work.
5. Call start, build_container, and description.

The functions in the final step are backend hooks. Core supplies Proxmox VE's pct path or Incus's incus path after platform detection—do not source either backend directly from an application script.

Use the detailed CT guide for the maintained template, variable ownership, app inputs, and update contract.