Hoody Daemons

The Hoody Daemon service provides programmatic control over background processes and long-running programs running inside your containers. Daemons let you manage supervised services — including web servers, workers, schedulers, and custom applications — through a unified API that handles lifecycle, state, and observability.

Use the Daemon API when you need to:

• Register a program as a supervised daemon and keep it running.
• Start, stop, enable, or disable services on demand.
• Inspect runtime status, logs, and process health without shell access.

The Daemon API is organized into three sub-pages, each focused on a distinct concern.

Available endpoints

Daemon Management

Create, read, update, and remove daemon programs registered with the supervisor.

Open Daemon Management →

Program Control

Enable or disable programs in the boot sequence and start or stop them at runtime.

Open Program Control →

Status & Monitoring

Retrieve live status and process information for a specific daemon program.

Open Status & Monitoring →

How it fits together

Note

Daemon operations are scoped to a single container. All requests must include the target container in the path, and the hoody-sdk resolves the correct base URL automatically based on the accessor you use.

A typical workflow follows this order:

1. Manage — Register the program with the supervisor using the management endpoints, providing the command, working directory, environment, and restart policy.
2. Control — Enable the program so it starts on boot, then use start/stop to manage its runtime lifecycle.
3. Monitor — Poll the monitoring endpoints to confirm the process is running, healthy, and behaving as expected.

Refer to the sub-pages above for the full parameter, request, and response details for each operation.