Skip to content
CLI

Deploy from the terminal with the CLI.

The CLI can detect, plan, execute, verify, and recover deployments from local projects or CI. It is also handy for hot fixes.

Entrypoint

Terminal

Best for

Local and BYOS

State

Control plane or ssh-pglite

Recovery

retry / redeploy / rollback

Supports Dockerfile, Compose, static output, prebuilt image, and workspace-command paths
Pure SSH can use server-owned ssh-pglite state when no control plane is selected
After deploy, continue with logs, health, diagnostics, and recovery readiness

Entrypoint selection

The CLI prefers repository Appaloft config when present. It can also choose paths from Dockerfile, Compose, static output directories, or image:// references.

Operation boundary

appaloft deploy maps to deployments.create. Durable source, runtime, network, and health configuration belongs to the Resource profile.

Recovery path

Follow deployments with appaloft logs, appaloft resource diagnose, recovery-readiness, rollback, retry, and redeploy operations. Leave direct server edits as the last resort.

Deployment flow

1

Detect

Read package metadata, Dockerfile, Compose, ports, start commands, and appaloft.yml.

2

Deploy

Upload, build, start, and record each step.

3

Verify

Check URL, HTTPS, health, logs, and rollback candidates.