Deployment Configuration

Reoclo stores application environment variables encrypted at rest and injects them only during deployment on the target server. Values are written to a secure temporary file with restrictive permissions and used for container startup, keeping secret handling in the worker execution path instead of the browser-facing control plane.

Health checks are a key part of release safety. Define a stable endpoint that reflects app readiness, not just process liveness. Reoclo polls this path after launching a new container and only finalizes cutover when checks pass, which makes rollback behavior predictable when startup regressions occur.

Docker builds happen on the destination host, so build context, Dockerfile assumptions, and host tooling directly affect deploy time and reliability. Because images are built and retained locally on each server, Reoclo avoids central registry dependencies while keeping artifact locality aligned with runtime execution.