Internals

How Taskhoster works inside. None of this is needed to use it, the usage guide and the rest of the reference cover that. This section is the full picture: the pieces that run, where every byte lives on disk, and the private APIs between them.

Topics

Local →

The local package's file map: the one command you run, the shared toolkit, the log tools, and the sync.

Server →

Caddy out front, the localhost-only API, and every file and directory a host keeps on disc.

Store →

The heart of it: one file per task under a state directory, the atomic-rename claim, the sweep, and the durable task-event log.

Sync →

The private management API the local package uses to mirror definitions up, endpoint by endpoint.

Tools →

The read-only API behind the Web, Server and Task log browsers.