@makerstufferupper/flypi 0.1.2 → 0.1.3

package/README.md

@@ -26,6 +26,26 @@ flypi stop
 The first start downloads two local models (~900 MB) for the memory store — an embedder and a
 contradiction judge. Skip them with `flypi start --embeddings none --judge none`.
 
+## Docker
+
+```bash
+docker build -t flypi .
+docker run -d --name flypi -p 127.0.0.1:8791:8791 -v flypi-data:/data flypi
+open http://localhost:8791/
+```
+
+No start command: the container starts the daemon and prints its URL in `docker logs`. `-v flypi-data:/data`
+is where `.flypi/` lives — conversations, the memory wiki, your config and the ~900 MB of models — so it
+survives the container being removed; without it the download and everything you wrote go with it. Bind
+`127.0.0.1:` unless you want the whole LAN to reach it: the page and `/healthz` are served without the token.
+
+`docker stop` shuts the daemon down properly (an in-flight turn is recorded as interrupted, never re-run).
+`docker exec flypi flypi status` and `... flypi logs -n 100` read the running daemon. `flypi update` does not
+work in a container — the package is read-only there; rebuild the image instead.
+
+The image installs the published package, so it is the same code `npm install -g` gives you;
+`docker build --build-arg FLYPI_VERSION=0.1.2` pins the version.
+
 ## Configure
 
 `.flypi/agent/models.json` names your providers and models, and `.flypi/agent/settings.json` picks

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@makerstufferupper/flypi",
-	"version": "0.1.2",
+	"version": "0.1.3",
 	"type": "module",
 	"description": "Local multi-model agent tool with a browser UI and a personal knowledge wiki, built on the pi SDK.",
 	"license": "MIT",

package/scripts/flypi.mjs

@@ -7,6 +7,7 @@
  * detached, wait until `/healthz` answers, and report the URL you would otherwise have to dig out of a log.
  *
  *   node scripts/flypi.mjs start [--foreground]   # or: npm run flypi -- start
+ *   node scripts/flypi.mjs start --foreground --port 8791 --host 0.0.0.0   # the container entry point
  *   node scripts/flypi.mjs status | stop | restart | logs [-n 50] [-f]
  *   node scripts/flypi.mjs update [--check]        # the newest published flypi (docs/architecture.md Phase 7)
  *
@@ -187,6 +188,12 @@ async function start({ foreground = false, previous } = {}) {
 	if (Object.keys(namedFlags).length > 0) writeFileSync(flagsPath, `${JSON.stringify({ ...readJson(flagsPath), ...namedFlags })}\n`);
 	if (foreground) {
 		const child = spawn(process.execPath, ["--import", "tsx", serveDaemon, "--root", root, ...flags], { cwd: checkout, stdio: "inherit" });
+		// Ctrl-C and `docker stop` reach this process, not the daemon. PID 1 in a pid namespace drops a signal it
+		// has no handler for, so without this the SIGTERM never arrives: docker waits out its grace period and
+		// SIGKILLs a daemon that never got to remove its pid file, close its sockets or record an interrupted
+		// turn. Installing the handler is what makes the signal be delivered; forwarding is what makes the
+		// daemon run its own shutdown, and the exit code comes from the daemon rather than from this wrapper.
+		for (const signal of ["SIGINT", "SIGTERM"]) process.on(signal, () => child.kill(signal));
 		return new Promise((done) => child.on("exit", (code) => done(code ?? 0)));
 	}
 	// The log's directory is created above, not assumed.

package/scripts/release.mjs

@@ -14,7 +14,10 @@ import { spawnSync } from "node:child_process";
 import { readFileSync } from "node:fs";
 
 const argv = process.argv.slice(2);
-const dryRun = argv.includes("--dry-run");
+// `npm run release patch --dry-run` hands `--dry-run` to npm, not to this script, but npm does export it as
+// config — so a "dry run" of the release really bumped the version, committed, tagged and pushed, and only the
+// publish was dry. Read both, so the flag means what it says whichever way it arrives.
+const dryRun = argv.includes("--dry-run") || process.env.npm_config_dry_run === "true";
 const kind = argv.find((a) => ["patch", "minor", "major", "preminor", "premajor"].includes(a)) ?? "patch";
 
 /** `remote: true` marks the two steps that leave this machine, so the dry-run output says which is which. */