Skip to content
Reoclo Reoclo Reoclo Docs

Application Groups

Application groups let you organize related applications that deploy from the same repository. When you push to a shared repository, you can deploy all applications in the group together with a single action.

This page covers manual groups. If a docker-compose file defines your services, use a stack instead. A stack deploys the services as one coordinated deployment.

When to Use Groups

Section titled “When to Use Groups”

Groups are useful when you have a monorepo with multiple services:

my-platform/
  api/           -> api application
  web/           -> web application
  worker/        -> worker application
  docker-compose.yml

Each service has its own Dockerfile and Reoclo application, but they all live in the same repository. A group lets you deploy all of them at once when you push.

Creating a Group

Section titled “Creating a Group”
  1. Navigate to Application Groups in the sidebar
  2. Click Create Group
  3. Configure:
    • Name: the form opens with a random name such as grp-brave-whale. Use Shuffle for another one, or type your own. The form tells you if the slug is already used.
    • Repository: the shared repository all member apps deploy from
    • Server: optionally set a shared deployment target
    • Auto-deploy: a group-level default. The auto-deploy setting on each application controls deploys on push.
  4. Click Create

Adding Applications to a Group

Section titled “Adding Applications to a Group”

When creating or editing an application, select the group it belongs to. The application will inherit the group’s repository if one is set.

Each application in the group has its own:

  • Dockerfile path (for example, ./api/Dockerfile, ./web/Dockerfile)
  • Container port
  • Health check path
  • Environment variables

Deploying a Group

Section titled “Deploying a Group”

Manual group deploy

Section titled “Manual group deploy”

From the group detail page, click Deploy All. Reoclo will trigger a deployment for every application in the group simultaneously.

The confirmation dialog has a Force recreate containers option. Select it to recreate the containers even when the image and the configuration did not change. This option applies to one deployment only.

The deploy summary shows:

  • Total applications
  • How many Reoclo triggered
  • How many Reoclo skipped (for example, no repository configured)
  • The deployment status of each application

Auto-deploy on push

Section titled “Auto-deploy on push”

Each member application has its own auto-deploy setting. If an application has auto-deploy on, a push to the shared repository deploys that application. Each application builds and deploys independently. If one deployment fails, the other deployments continue.

Stacks

Section titled “Stacks”

If a docker-compose file defines your services, use a stack instead of a manual group. A stack creates one member application per compose service and deploys them together in dependency order. See Stacks for the full guide.

Managing Groups

Section titled “Managing Groups”
  • Edit: Update the name, repository, server, or auto-deploy setting
  • Delete: Deleting a group unlinks all member applications. The applications remain but are no longer grouped.

Next Steps

Section titled “Next Steps”