Reference
The exact contracts the usage guide describes: the field types a schema can use, the queue definition format, the HTTP API and the WebSocket sockets, the files a host keeps, the shared hoster machinery, and how the task store works inside (Internals). Every name across the reference is also a search record below.
Contents
Types →
The field types a schema can use: what each accepts and how it is stored.
Definition →
The complete queue-definition JSON: every setting and default, the access rules, and the three schema blocks.
API →
Every HTTP endpoint (producer, worker and management) with example requests and responses, and the criteria operators.
Sockets →
The two WebSocket protocols in full: monitor (subscribe / status) and work (claim / progress / result).
Files →
Every fixed taskhoster- file and folder a host keeps, on your machine and on the
server.
Internals →
How the task store works inside: one file per task, the atomic-rename claim, the sweep, and the durable event log.
Hoster →
The machinery every hoster shares: the local package, the server, sync and the tools.