Deployments Overview

Reoclo deployments follow a deterministic pipeline: trigger, queue, worker execution, and target-host rollout. A deployment can start from a manual action in the dashboard or from a GitHub push webhook routed through the gateway. In both cases, Reoclo records a deployment object before execution begins.

Jobs are published to RabbitMQ and consumed by the worker service, which executes deployment steps against the selected server using SSH or Runner transport. The worker performs prechecks, clones the repository with a short-lived GitHub installation token, and builds the Docker image directly on the target host.

Runtime cutover uses blue-green style replacement with health checks. Reoclo starts the new container, polls the configured health endpoint, and removes the old runtime only after success. If checks fail, the previous container is restarted and the deployment is marked failed for operator visibility.