Skip to content
devopsellence docs

Deploy with shared

Shared mode keeps the same root verbs as solo, but the control plane owns organization, project, environment, release, token, and node coordination.

Terminal window
devopsellence init --mode shared
devopsellence node create prod-1 --provider hetzner
devopsellence deploy --dry-run
devopsellence deploy
devopsellence status

Register an existing server when the VM already exists:

Terminal window
devopsellence node register

By default, registration generates a token scoped to the current environment. Run the output command on the server to install the node agent and attach the node.

CloudStack VMs use this existing-server path today. See CloudStack VMs.

Shared mode is the right default when API tokens, browser auth, team workflows, and hosted/self-hosted coordination are part of the product requirement.