Skip to main content
Use the CLI when you want to run the same application-delivery workflow directly. You need the URL of Stackdome Cloud or a self-hosted installation and an API token created for your account. Read authentication and API tokens before handling credentials. To understand or extend the generated configuration, use the Stackfile reference.

​
Deploy the repository

Run these commands from the repository root:
stackdome whoami -o json verifies the active server, signup-created organization, default project, and authentication method before deployment. Organization and project selection are not part of the alpha workflow. stackdome init converts a Compose file when one is present or creates a starter stackfile.yaml; edit that generated file from evidence in the repository, then run stackdome validate again before deploying. stackdome deploy --wait -o json waits for a terminal release state. It exits non-zero unless the release reaches Released. Retain the returned release.id as the deployed release ID and require release.state to be Released. In the status result, require converged_release.id to equal that deployed release ID, converged_release.state to be Released, and converged_release.health to be ok. If you also claim it is still the newest attempt, require latest_release.id to equal the deployed release ID and latest_release.state to be Released. For a public service, return its URL without opening a browser:
The urls array contains the public resource URLs. A service with no public port is not expected to return one.

​
Structured output

With -o json or -o yaml, stdout contains only structured result data. Progress, prompts, warnings, and other prose are written to stderr, so automation can parse stdout without stripping human-readable messages. Use stackdome <command> --help to verify flags before adding commands to automation.

Stackdome Cloud during alpha

Review Cloud availability, ephemerality, and the self-hosted fallback.