Handbook
Build 201 — Integration recipes index
Pick a row, gather the prereqs, open the guide, and validate the expected output before deep-diving Examples & recipes.
Updated
| Use case | Who | Prerequisites | Guide | Expected output |
|---|---|---|---|---|
| Health / version probes | SRE, integrator | Fleet listening | Quickstarts · curl examples | GET /v1/version and /v1/health return 200 JSON |
Hello-world docker_argv job |
Developer | Docker on Fleet host | First job · jobs examples | HTTP 201 create; job completed |
| Stateful job + workspace tarball | Integrator | Workspace manifest policy understood | Workspace upload · workspace examples | meta.workspace_state becomes ready; runner starts |
| Template-backed images | Platform | Docker + buildx policy | Container templates · examples | Resolve/build succeeds; job uses rewritten image |
| TLS / Caddy front | Operator | DNS + certs | Caddy + systemd · Caddy healthcheck example | https://host/v1/health OK |
| Granite / unified hostname | Operator | Multiple backends | Caddy unified Granite | Single hostname routes to Fleet + peers |
Managed forge_llm service |
Integrator | Compose stack available | HTTP API · managed services example | Service start/stop via API |
| Operator visibility | Operator | Bearer for snapshot | Admin + Studio | GET /v1/admin/snapshot reflects live jobs |
| Remote git self-update | Maintainer | Host shell + git layout | Upgrade & remote ops · self-update example | POST /v1/admin/git-self-update ok: true or documented 400 hand-off |
When wiring Forge Lenses / Studio, start with Admin dashboard & Studio so tokens + URLs land in LENSES_FLEET_*.
Language starters: Examples hub (Python / TypeScript / CI smoke).