Steward v0.1.1
Fixes an install that could not complete. v0.1.0 is not installable — it builds the gateway from a floating upstream tag that has since moved, and the Dockerfile's checksum guard correctly stops the build.
curl -fsSL https://raw.githubusercontent.com/FrontAnalyticsInc/steward/main/install.sh | bashNot sudo bash. Ubuntu 22.04/24.04 x86_64, 8 GB RAM, 40 GB free where Docker writes. Budget 20–40 minutes for the build.
Everything here came from installing v0.1.0 on a clean box:
- Upstream gateway image pinned by digest.
:latestmoved and broke every fresh install; a machine with the layer cached kept building green, which is how it got past CI. - The stack file is rendered interpolated, so compose can read it back. Un-interpolated, every bind mount rendered as an undeclared named volume and the whole project was rejected at
up. - Compose v2 is installed, not just required.
- The docker group no longer ends the install — it re-enters with the group applied.
- The sudo password is read from the terminal, not from the script the pipe is feeding it.
- RAM is reported without losing a gigabyte to truncation. An 8 GB box said 7 and was warned; a 6 GB box said 5 and was refused.
- No Anthropic key no longer stops the install. It builds and starts so the console is reachable, then says plainly that nothing can call a model until you add one.
- The install ends by telling you how to open the console, including Tailscale setup for this machine and the one you browse from.
The console on :9120 still has no authentication. Leave DASHBOARD_BIND at 127.0.0.1 and reach it over a tailnet or an SSH tunnel.