Skip to main content
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:
Most provisioning operations require root. They also expect the managed-host layout to have been staged already: a validated /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
Validate the host application manifest
Converge managed project ownership and modes
Prepare verified application source checkouts
Run a validated lifecycle for managed applications

Runtime and host configuration

Configure the managed host account and runtime paths
Prepare and persist managed host filesystems
Mount declared read-only production volume overlays
Install verified Docker Compose and Buildx CLI plugins
Install the managed sitectl runtime
Install the complete verified sitectl package and artifact set
Install verified managed host artifacts
Install every artifact in the root-owned manifest
Enforce the managed host runtime trust boundary
Normalize and verify managed runtime ownership and modes

Environment files

Manage host-owned environment files
Atomically set a host environment value
Atomically set a managed Compose environment override
Reconcile application environment data into a Compose dotenv file

Services and readiness

Converge Cloud Compose systemd services
Start host bootstrap when its readiness marker is absent
Start a oneshot unit and wait for its terminal state
Remove retired Cloud Compose systemd units
Manage Cloud Compose readiness markers
Check whether a readiness marker is safe and valid
Publish a root-owned readiness marker
Validate and consume a fresh-filesystem marker
Report whether application initialization is required
Require durable or current-boot application initialization
Initialize or check the managed Vault Agent
Manage Vault Agent sink-token readiness
Run the validated managed rollout service

Backups and maintenance

Run managed backup and recovery operations
Create daily MariaDB recovery artifacts
Hand complete recovery coverage to the off-host driver
Prove the latest off-host backup in disposable recovery
Run managed host maintenance
Prune old unused Docker data

GCP host operations

Configure GCP host and container metadata isolation
Rotate managed GCP service-account keys
Converge every enabled managed service-account key
Operate app service-account credentials
rotate app service-account credentials
rollback app service-account credentials
retire app service-account credentials
Operate internal service-account credentials
rotate internal service-account credentials
rollback internal service-account credentials

Diagnostics

Inspect managed host provisioning state
Print managed host status
Print the bootstrap state
Print managed host dump