Handbook

Start here — Forge Fleet docs

Pick the track that matches your role. Each link jumps to the right handbook page inside the Start structure.

Updated

Fleet in one view

Text-only sketch (a Kitchen Sink network / linear diagram will mirror this in What is Fleet? — track status in docs/maintainers/VISUAL-COVERAGE.md):

  1. Client (curl, Studio, scripts) calls POST /v1/jobs with kind: docker_argv.
  2. Fleet stores the row in SQLite, optionally waits for workspace upload, then spawns the runner.
  3. Docker / Podman executes argv; stdout/stderr stream back into the job row for GET /v1/jobs/{id}.
I want to… Go to
Run Fleet locally on my machine (dev loop) Install locally · Quickstarts · Your first job · Repository README
Install Fleet on a fresh host (systemd, Docker) Host bootstrap · Git install · Caddy + systemd
Call the HTTP API from scripts or curl HTTP API reference · Examples hub · Schemas
Integrate Lenses / Studio (workspace, Test Fleet) README (Fleet env summary) · Forge LCDL vs Fleet · Workspace upload · Admin + Studio
Use requirement templates and container images Container templates
Put Fleet behind TLS / Caddy (incl. unified Granite) Caddy + systemd · Caddy unified Granite
Release or self-update Fleet on a box I maintain Repository README (Remote automation) · Upgrade & remote ops

Verification triad (any track): after the server is up, GET /v1/version and GET /v1/health should return JSON—see Examples & recipes or Quickstarts.

Concept map: What is Fleet? (+ Start hub overview).

Next track: when installs feel solid, continue to Learn 101 hub → Build 201 → Operate 301 → Reference.