Daemon

The Phlo Daemon is the optional sidecar that runs your app on a pool of resident workers. It is what makes async calls, scheduled tasks and Phlo Realtime fast, while core Phlo keeps working without it. This mini-manual covers the execution modes, the worker pool, the dispatch API and how Phlo Realtime couples to it.

1Daemon overviewThe Phlo Daemon is an optional Node sidecar (phlo-daemon.js) that runs any Phlo target on a pool of resident workers. It is a generic engine: it knows nothing about WebSockets, tasks or any one feature. Phlo Realtime and the scheduler are built into the daemon; the runtime helpers reach it over local HTTP. Core Phlo works without it; the daemon is the layer that makes the heavy paths fast and powers the long-lived services. 2The worker poolThe daemon keeps a pool of resident PHP workers per app. Each worker boots the app once and then answers many calls, removing the per-call boot that the one-shot path pays. It is the same idea as FrankenPHP's HTTP worker mode, but for non-HTTP work. 3The dispatch APIThe daemon's main endpoint is POST /dispatch. It binds 127.0.0.1 by default, so it is local-only; gate it at the network boundary. 4Runtime helpers and schedulingTwo consumers ride the daemon without you calling /dispatch yourself: the async runtime helpers, and the scheduler. 5The WebSocket layerPhlo Realtime is the daemon's built-in WebSocket server: the daemon owns the sockets and runs your PHP hooks in the same process. This is how that fits together, and a good model for how the daemon's features relate.