gantry: Skill for Claude Code

Deploy and Release — Gantry

Full walkthroughs (Cloudflare Tunnel, nginx/Caddy configs, systemd unit): docs/deployment.md. This skill covers what's actually wired in CI/CD, the exact scaffolding behavior, and gaps between docs and code. For build mechanics (esbuild config, bun run dev's "stale client bundle" trap, binary packaging internals) see the build-and-dev skill — not duplicated here.

Three deployment shapes

All three serve one Express process on port 3100 (PORT/GANTRY_PORT), one FLEET_DIR per process, one SQLite file ($FLEET_DIR/data/fleet.db). Only one Gantry instance may run against a given FLEET_DIR — SQLite lock contention otherwise (see docs/getting-started.md "Database locked" troubleshooting entry).

docker-compose.yml (verified against the actual file)

services:
  gantry:
    build: { context: ., dockerfile: Dockerfile }
    image: gantry:local
    ports: ["${GANTRY_PORT:-3100}:3100"]
    volumes: ["${FLEET_DIR:-./_data}:/data"]
    environment:
      - FLEET_DIR=/data
      - LOG_LEVEL=${LOG_LEVEL:-info}
      - TRUST_PROXY=${TRUST_PROXY:-0}
      - GANTRY_SECRET=${GANTRY_SECRET:-}
    restart: unless-stopped
    healthcheck: { test: ["CMD", "curl", "-sf", "http://localhost:3100/health"], interval: 30s, timeout: 5s, retries: 3, start_period: 10s }

Single named volume mount at /data — that's the entire persistence surface: gantry.json, fleet-credentials.enc.json, data/fleet.db, logs/, agent prompt .txt files. Host-side path comes from $FLEET_DIR env var (defaults to ./_data next to the compose file) — this is a host path substituted into the bind mount, separate from the container's FLEET_DIR=/data env var baked into the environment: block. Don't confuse the two when debugging "my config isn't picked up" — the container always reads /data regardless of what the host-side $FLEET_DIR was set to.