Skip to content
Reoclo Reoclo Reoclo Docs

reoclo groups

reoclo groups ls
reoclo groups get <group>
reoclo groups deploy [options] <group>
reoclo groups redeploy <group> <service>
reoclo groups run [options] <group> <service>
reoclo groups task-runs [options] <group>
reoclo groups deployments [options] <group>
reoclo groups deployment [options] <group> <numberOrId>

reoclo stacks is an alias for reoclo groups. A stack is a definition group: one docker-compose file, one member application for each service, one coordinated deployment.

<group> accepts the group’s slug or its id.

ls

Section titled “ls”

Lists every group with its kind, member count, CI gate state, and last deployment.

Terminal window
$ reoclo groups ls
SLUG        NAME        KIND     APPS  CI   LAST DEPLOY
portfolio   Portfolio   compose  4     on   #12 succeeded

get

Section titled “get”

Shows one group as a full object, including the deploy branch, the CI gate toggle, and the compose file path.

prune

Section titled “prune”

Removes members whose service left the compose definition. Without --yes, the command only lists the orphaned members.

Terminal window
$ reoclo stacks prune portfolio
SLUG                SERVICE   STATUS
portfolio-postgres  postgres  stopped
Re-run with --yes to remove 1 orphaned member(s).


$ reoclo stacks prune portfolio --yes
✓ removed portfolio-postgres

Reoclo removes the member with the same soft-delete semantics as the dashboard. Secret bindings and environment variables on the other members are not touched.

deploy

Section titled “deploy”

Triggers one coordinated deployment of every managed member (the dashboard’s Deploy All).

  • --force-recreate recreates every container, even when the image and the configuration did not change. Without it, the deploy leaves unchanged services running.
  • --wait polls the deployment, prints each stage as it changes, and exits non-zero when the deployment does not succeed.
  • --wait-timeout <seconds> gives up after this long (default 600).

redeploy

Section titled “redeploy”

Redeploys one compose service of the stack as a scoped group deployment.

  • --force-recreate recreates the named service’s containers, even when the image and the configuration did not change. Other services are not touched.
Terminal window
$ reoclo groups redeploy portfolio backend

run

Section titled “run”

Runs a one-shot task member: a compose service under profiles: or with the reoclo.task label, for example a database migration. Reoclo runs docker compose run --rm on the server with the stack’s environment files applied. Exit code 0 is success.

  • --wait polls the run, prints its exit code and last log lines, and exits non-zero when the run fails.
  • --wait-timeout <seconds> gives up after this long (default 600).
Terminal window
$ reoclo groups run portfolio minio-init --wait
task minio-init: succeeded (exit 0)
Bucket created successfully local/dev

Deploy the stack one time before you run a task. The run uses the environment files from the last stack deployment.

task-runs

Section titled “task-runs”

Lists the stack’s one-shot task runs, newest first, with status, exit code, and duration.

  • --limit <n> caps the rows (default 20).

deployments and deployment

Section titled “deployments and deployment”

deployments lists the stack’s coordinated deployments. deployment <group> <numberOrId> shows one deployment with its stages and per-service slices.

  • --logs on deployment also prints each stage’s captured log tail, including the failure diagnostics (failing service state and last log lines).

Next Steps

Section titled “Next Steps”