stackdome CLI to turn repository evidence into a Stackfile, deploy to Stackdome Cloud or a self-hosted installation, verify runtime health, and return the public URL.
The canonical flow is:
Before the agent starts
The agent needs the repository, the destination URL, and an API token. The user creates and revokes tokens; the agent never requests or handles an account password. See authentication and API tokens.Install the Stackdome deploy skill.
Operational flow
1
Inspect the repository
Read the Dockerfile, Compose file, package or build configuration, documented startup command, ports, and required environment variables. Use repository evidence instead of assuming a runtime.
2
Initialize the Stackfile
Run
stackdome init. It converts a supported Compose file when present or creates a starter stackfile.yaml. Never author the file from memory before running the initializer.3
Edit the generated Stackfile
Replace starter values with the source, build, command, ports, environment, dependencies, and storage requirements found in the repository. Use the Stackfile reference for the grammar.
4
Validate until clean
Run
stackdome validate after each edit and correct every reported error. The validator is the authority for the installed CLI version.5
Authenticate with a token
Use
stackdome login --url https://<your-stackdome-host> --token <api-token>, then run stackdome whoami -o json to verify the active host and scope.6
Deploy and wait
Run
stackdome deploy --wait -o json. Structured result data stays on stdout; release events and progress go to stderr. Retain the non-empty release.id as the deployed release ID. A non-zero exit or release.state other than Released is a failed deployment.7
Verify current status
Run
stackdome status -o json. Require converged_release.id to equal the deployed release ID, converged_release.state to be Released, and converged_release.health to be ok. Before calling this the newest release, also require latest_release.id to equal the deployed release ID and latest_release.state to be Released.8
Return the public URL
For a public service, run
stackdome open -o json and return at least one entry from urls. If no URL is returned, check that the Stackfile declares a public port before claiming the application is reachable.Failure routes
Start with the command for the stage that failed. Read its result before changing the Stackfile or retrying the release.
Use the retained release ID returned by
stackdome deploy -o json for status equality checks and release events. Use the build ID returned by stackdome build list for build information and logs.
stackdome status -o json returns structured release state and health for automation. Run stackdome status --conditions separately when a person needs full condition history.
Preserve the deployment definition
Once the release passes every check, ask the user to commitstackfile.yaml with the application code. That file keeps the Cloud and self-hosted deployment workflow reproducible in later sessions.
Quickstart with an agent
Start with the shared prompt and the Cloud fallback path.
Use the CLI directly
Run the same validated sequence without an agent.