reoclo apps
reoclo apps lsreoclo apps get <idOrSlug>reoclo apps deploy [options] <idOrSlug>reoclo apps logs [options] <idOrSlug>reoclo apps restart <idOrSlug>Lists every application in the active tenant with its slug, target server, last deployment status, and current deployment ref.
$ reoclo apps lsSLUG SERVER LAST DEPLOY REFapi prod-web-1 ✓ succeeded deadbeefworker prod-web-1 ✓ succeeded deadbeefdocs staging-web ✓ succeeded abc1234admin prod-web-1 ✗ failed cafe999get <idOrSlug>
Section titled “get <idOrSlug>”Shows the full application record: server, repository, build configuration (Dockerfile, Nixpacks, or buildpack), deployment policy, attached domains, and the most recent few deployments.
reoclo apps get apireoclo apps get 019dc1a8-841f-7102-ac5d-3ee9e9353795deploy [options] <idOrSlug>
Section titled “deploy [options] <idOrSlug>”Triggers a deployment for an application. Returns once the deployment has been queued; pass --wait (when shipped) to block until the deployment finishes.
| Flag | Description |
|---|---|
--ref <commit> | Deploy a specific commit, branch, or tag (default: the configured branch’s HEAD). |
--wait | Wait for the deployment to reach a terminal state. (Coming in v1.x.) |
reoclo apps deploy apireoclo apps deploy api --ref v2.4.1reoclo apps deploy api --ref $(git rev-parse HEAD)After triggering, fetch the deployment logs:
LATEST=$(reoclo deployments ls --app api --limit 1 -o json | jq -r '.[0].id')reoclo deployments logs --build "$LATEST"logs <idOrSlug>
Section titled “logs <idOrSlug>”Fetches recent container logs for an application. The container name is resolved automatically from the application record (it uses the linked_container_name if set, otherwise the canonical reoclo-{tenant}-{slug} derivation).
| Flag | Default | Description |
|---|---|---|
--tail <n> | 200 | Number of lines to return. |
--since <ts> | (none) | RFC 3339 timestamp; only return lines after this time. |
--search <term> | (none) | Substring filter applied server-side. |
reoclo apps logs api --tail 500reoclo apps logs api --search 'error'reoclo apps logs api -o json | jq '.entries[] | select(.level == "error")'For full server-wide log access including non-application sources (system journal, runner, etc.), use reoclo logs tail.
restart <idOrSlug>
Section titled “restart <idOrSlug>”Restarts the container backing an application by issuing docker restart against the resolved container name. Returns the container name and the runner’s exit code; non-zero exit codes propagate as a CLI failure.
reoclo apps restart apirestart is one of the few commands available to Automation Keys; see CI/CD automation.
Automation keys
Section titled “Automation keys”reoclo apps deploy is one of the few commands available to Automation Keys. See CI/CD automation for examples.
Exit codes
Section titled “Exit codes”| Code | Meaning |
|---|---|
| 0 | Deployment queued (or, with --wait, succeeded) |
| 1 | Network or server-side error |
| 3 | Authentication failure |
| 4 | Key type not allowed for this command |
| 5 | App not found |
Related
Section titled “Related”reoclo deployments— view deployment historyreoclo env— manage environment variables for an appreoclo logs tail— tail container logs