Entrypoint selection
The CLI prefers repository Appaloft config when present. It can also choose paths from Dockerfile, Compose, static output directories, or image:// references.
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 guidance
Configuration boundary
appaloft deploy starts the deployment. Durable source, runtime, network, and health configuration belongs in the Resource profile.
Recovery path
Follow deployments with appaloft logs, appaloft resource diagnose, rollback, retry, and redeploy. 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.
Related topics
Keep following the same deploy path.
Appaloft SEO pages are organized around real deployment tasks. Each page should lead to the next useful step, not stand alone.
Own server deployment
Tie the control plane, CLI, servers, rollback, and Cloud collaboration boundary into one self-hosting cluster.
GitHub deployment
Use GitHub Actions to connect repository events to Appaloft deployment while keeping explicit workflows.
Static site publishing
Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.
AI deployment
Let the agent identify project shape first, then choose the skill, CLI, static publishing, or Cloud console path.