Skip to content
devopsellence docs

Deploy with solo

Solo deploy scope comes from nodes attached to the current workspace and environment.

Terminal window
devopsellence node attach prod-1
devopsellence deploy --dry-run
devopsellence deploy
devopsellence status

The CLI builds locally, transfers or loads the image for each node, writes desired state, and lets the node agent reconcile.

Useful inspection commands:

Terminal window
devopsellence doctor
devopsellence node diagnose prod-1
devopsellence logs --node prod-1 --lines 100
devopsellence node logs prod-1 --lines 100
devopsellence support bundle --output ./devopsellence-support.json

support bundle writes a local, redacted JSON evidence file with workspace config, solo state shape, attached nodes, CLI version, and recommended follow-up commands.

For app data, use an ordinary backup service with restic and the existing secret, deploy, logs, and exec commands. See Backup and restore.

For Redis, Memcached, and other companion containers, add another service with a custom image. See Supporting services. Release tasks that need a companion service should also account for service readiness before running migrations or setup commands.

To create a Hetzner-backed solo node:

Terminal window
devopsellence provider login hetzner --token "$HCLOUD_TOKEN"
devopsellence node create prod-1 --provider hetzner --install --attach
devopsellence doctor

For CloudStack, create the VM through CloudStack and add it as an existing SSH node. See CloudStack VMs.