Handbook

Learn 101 — Operator apt install (no git)

Outcome: Fleet user cockpit on a fresh Ubuntu 24.04 (noble) machine without git clone.

Updated 2026-10-22

Audience: laptop operators and mesh cockpits. Contributors still use git install.

Placeholders

Placeholder	Default when unset
`<FLEET_APT_REPO_URL>`	`https://packages.forgesdlc.com/fleet/ubuntu`
`<FLEET_APT_SUITE>`	`noble`

Override for staging:

export FORGE_APT_BASE_URL="https://<FLEET_APT_REPO_HOST>/fleet/ubuntu"

Laptop (user package, port 18766)

curl -fsSL "${FORGE_APT_BASE_URL:-https://packages.forgesdlc.com/fleet/ubuntu}/install.sh" \
  -o /tmp/forge-fleet-install.sh
bash /tmp/forge-fleet-install.sh --user
land-fleet setup-user
curl -fsS http://127.0.0.1:18766/v1/health

With Docker (optional local worker):

bash /tmp/forge-fleet-install.sh --user --with-docker

System node (port 18765)

sudo bash /tmp/forge-fleet-install.sh --system --with-docker
curl -fsS http://127.0.0.1:18765/v1/health

Cooperative upgrade (apt)

After install, the deb postinst enables forge-fleet-apt-upgrade.timer. Routine bumps:

Open /admin/ → Update Fleet, or
POST /v1/admin/upgrade with bearer, then land-fleet upgrade --wait.

Fleet drains dependents first, writes an upgrade signal, and the root timer runs apt-get install within ~60s.

Check timer: land-fleet timer-status.

Migrate from git

Existing git_user / git_system installs: 10-migrate-to-apt.md.

Use bash install.sh --user --migrate-from-git (or system equivalent) once, then land-fleet migrate-to-apt.

Next step

Connect to an existing remote Fleet: 08-connect-remote-fleet.md.

Forge Fleet