v0.2.6

insforge local start

Run a full InsForge backend in Docker on your own machine — Postgres, PostgREST, the backend, and the edge-functions runtime. No account, no repository clone.

npx -y @insforge/cli@latest local start

A hosted project remains the default for everything else. local is for when you specifically want a backend on your own machine; nothing routes to it on its own.

• local start — start, wait for health, link the directory, seed .env.local. --storage <local|minio|rustfs>, --pull, --port-*.
• local status — health, ports, backend version, per-container state. Keys masked unless --show-keys.
• local stop — --delete-data removes the volumes (gated critical by the human-in-the-loop guard), --unlink restores a displaced cloud link.

Where the stack comes from

The first start fetches deploy/setup.sh from the InsForge repository and runs it into .insforge/checkout/, then runs the compose file that script wrote — the same one self-hosting uses. The CLI adds one overlay: the telemetry stamp, and loopback binding for the published ports.

Secrets are generated by that script into .insforge/checkout/.env and read back. If the file goes missing while volumes still exist, local start refuses rather than generating new ones — Postgres reads its password only at cluster creation.

One instance per directory: the compose project name carries a hash of the directory path. The first instance gets ports 7130 / 7131 / 7133 / 5432 / 5430; when those are taken the block shifts by ten and start prints what moved.

Requires Docker with Compose 2.24.4 or newer.

No other changes

No command or flag was removed or altered. Every one of the 631 command/flag entries in 0.2.5 is present in 0.2.6, and 13 read commands produce byte-identical output against the same backend on both versions.