Daemon Management
Define and maintain the set of daemon programs on a container. Create new programs, update their command and environment, list every configured daemon, and remove entries that are no longer needed.
Daemons
Section titled “Daemons”The Hoody Daemon service provides API access to background process management, enabling you to programmatically define, control, and monitor long-running programs across your Hoody environment. Daemons are persistent processes managed by the platform lifecycle — they start on container boot, restart on failure, and expose their status for observability.
Use the Daemon API when you need to:
- Register a new background service (for example, a worker, scheduler, or sidecar proxy) and keep its configuration in sync with your application code.
- Toggle a program between enabled and disabled states, or trigger an immediate start or stop outside the normal lifecycle.
- Poll program status, retrieve uptime metrics, and inspect recent log output for operational dashboards and alerting.
The Daemon API is split into three logical groups:
Program Control
Drive runtime state changes for a daemon program. Enable or disable a program so the platform decides whether to launch it, or issue an explicit start or stop to override the current state.
Status & Monitoring
Inspect what a program is doing right now. Retrieve live status, process identifiers, and recent log lines to power dashboards, health checks, and incident response.
All Daemon API operations are scoped to a specific container, so requests must be authenticated with a token that has access to the target container’s project. Responses follow the standard Hoody API envelope: a JSON body with a top-level data object on success, or a statusCode / error / message structure on failure.