sitectl host exposes the same tested host-runtime operations used by Cloud
Compose so another provisioning system can assemble and operate a compatible
Linux VM without reimplementing them in shell.
Unlike commands that target a saved sitectl context, host acts on the machine
where the command runs. Connect to the VM first or invoke it over SSH:
/home/cloud-compose/.env, an
application manifest, systemd units, and the declared persistent disks. The
commands are composable provisioning primitives, not a one-command installer
for an arbitrary server.
Start with the read-only diagnostics and manifest validation commands. Before
changing filesystems, credentials, backup state, firewall rules, or systemd
units, confirm the target VM and review the command’s flags.
Reference
Provision and operate the current VM using sitectl’s managed-host layout. These commands run on the target host rather than through a saved sitectl context. They manage host filesystems, runtime tools, application manifests, systemd units, backups, credentials, and diagnostics. Most provisioning operations require root and an existing host environment file and application manifest.Applications
Operate the host application manifest
Prepare verified application source checkouts
Run a validated lifecycle for managed applications
Runtime and host configuration
Configure the managed host account and runtime paths
Mount declared read-only production volume overlays
Install verified Docker Compose and Buildx CLI plugins
Install the managed sitectl runtime
Install verified managed host artifacts
Enforce the managed host runtime trust boundary
Environment files
Manage host-owned environment filesServices and readiness
Converge Cloud Compose systemd services
Start a oneshot unit and wait for its terminal state
Remove retired Cloud Compose systemd units
Run the validated managed rollout service

