Skip to content
docs.deliberate

Install and sign in

View Markdown

Create your account and Team in the console. Install the CLI when you want to deploy an application from a local checkout or CI. You can deploy maintained Blueprints entirely from the console.

Install the CLI

Section titled “Install the CLI”

The installer selects the current release for your operating system and architecture, verifies its checksum, and installs it as deliberate:

Terminal window
curl -fsSL https://get.deliberate.cloud | sh
deliberate version

The default destination is /usr/local/bin; the installer asks for sudo only when that directory is not writable. To keep the installation entirely inside your home directory instead:

Terminal window
curl -fsSL https://get.deliberate.cloud | sh -s -- --install-dir "$HOME/.local/bin"

Ensure $HOME/.local/bin is on your PATH when using the second form. Later, upgrade the installed binary with:

Terminal window
deliberate update

Sign in

Section titled “Sign in”
Terminal window
deliberate login

The CLI shows a verification URL and code and opens the browser when possible. Sign in there; the CLI stores the resulting session in your user configuration directory. It does not place credentials in the Project checkout.

Confirm the active identity:

Terminal window
deliberate whoami

Select a Team

Section titled “Select a Team”

Every Project belongs to a Team. List the Teams available to your account and select the one you intend to deploy into:

Terminal window
deliberate team list
deliberate team use <team-slug>
deliberate team show

The selection persists for later commands. Commands that read a team: from Project configuration still validate that it matches a Team you can access.

Log in to the image registry

Section titled “Log in to the image registry”

You need this step only when pushing your own images. A maintained Blueprint can be deployed from the console without a local container runtime.

Terminal window
deliberate registry login

The command mints a time-limited, Team-scoped push credential and logs in the first supported runtime it finds. Docker is preferred; select another runtime explicitly when needed:

Terminal window
deliberate registry login --runtime podman
deliberate registry login --runtime nerdctl

The command prints the registry hostname and Team image prefix after a successful login. Workloads in the Team receive pull access automatically; do not copy the push credential into .deliberate/ YAML.

You are now ready to deploy your application or deploy a Blueprint.

Next steps

Section titled “Next steps”