@rindle/cli 0.4.3 → 0.4.4

package/README.md

@@ -15,73 +15,35 @@ This is the network counterpart of [`@rindle/replica`](../replica): both run the
 whereas `rindled` is the standalone daemon **executable** that serves many clients over the wire.
 Talk to a running daemon from JS with [`@rindle/daemon-client`](../daemon-client).
 
-> The all-TypeScript [`@rindle/server`](../reference/server) is the *reference* implementation of
-> the same wire protocol; `rindled` is its production replacement.
-
-## Install & run
-
 ```sh
 npm i -D @rindle/cli
-npx rindle init      # scaffold daemon.json
+npx rindle init      # scaffold daemon.json + migrations/
 npx rindle up --migrate --gen shared/schema.gen.ts --watch
 # start + supervise rindled, apply migrations, regenerate the typed schema,
 # and re-run apply/gen whenever migrations/ changes
 ```
 
-`rindle up` prints the address the daemon is reachable at (default `http://127.0.0.1:7600`) and how
-to talk to it. From another terminal:
-
-```sh
-npx rindle status                 # inspect the running daemon
-```
-
-…or from your app, via [`@rindle/daemon-client`](../daemon-client) pointed at the same URL.
-
 Installing pulls in exactly one prebuilt-binary package for your platform via
 `optionalDependencies` (the esbuild/napi pattern) — nothing is compiled, and the other platforms'
 binaries are never downloaded.
 
-### `npm run rindle` / `npm run rindled`
-
-`npm run <name>` runs a **script**, so add this to *your* `package.json` to drive `rindle` through
-your package scripts:
-
-```jsonc
-{
-  "scripts": {
-    "rindle": "rindle"
-  }
-}
-```
+## Docs
 
-Then `npm run rindle up`. (Or skip the script and use `npx rindle …` directly — the bin is on your
-`node_modules/.bin`.) The daemon is run by `rindle up`, not as its own command — see below.
+Full docs — the command reference, flags & env vars, the local dev loop, and remote-daemon usage:
+**[rindle.sh/docs/rindle-cli](https://rindle.sh/docs/rindle-cli)** · markdown mirror:
+[`rindle-cli.md`](https://rindle.sh/docs/rindle-cli.md) · for agents:
+[llms.txt](https://rindle.sh/llms.txt)
 
+## Embedding the daemon in your own supervisor
 
-### One-command app loop
-
-`rindle up` can now own the whole daemon-side development loop:
-
-```sh
-npx rindle up --migrate --gen shared/schema.gen.ts --watch
-```
-
-That starts and supervises the local `rindled`, waits until it is ready, applies pending
-`migrations/*.sql`, regenerates the `@rindle/client` schema TypeScript, and then watches the
-migrations directory. On each change it re-applies and re-generates; keep your app server/Vite
-process in a separate terminal. Drop `--watch` for a one-shot apply/gen, or use only
-`--migrate` / only `--gen <out>` if your workflow splits those steps.
-
-## The daemon (`rindled`)
-
-`rindled` is **not** exposed as a CLI command here — this package is a dev convenience, and `rindle
-up` is the way to run a local daemon. The binary still ships (co-located with `rindle`), so for
-embedding it in your own Node supervisor there are programmatic helpers:
+`rindled` is **not** exposed as a CLI command here — `rindle up` is the way to run a local daemon.
+The binary still ships (co-located with `rindle`), so for embedding it in your own Node supervisor
+there are programmatic helpers:
 
 ```ts
 import { spawnRindled, rindledBinaryPath } from "@rindle/cli";
 
-const child = spawnRindled(["--config", "./rindled.toml"]); // inherits stdio
+const child = spawnRindled(["--config", "./daemon.json"]); // inherits stdio
 // …or just locate the binary and manage the process yourself:
 const bin = rindledBinaryPath();
 ```
@@ -143,7 +105,3 @@ node scripts/build-npm-packages.mjs --bin-dir ./bins --version 0.1.0 --update-ro
 `--update-root` writes this package's `version` + `optionalDependencies` in lockstep. Then publish
 each `npm/<key>` package, then the umbrella. (The binaries + targets live in `package.json` under
 `"rindle"`, the single source of truth shared by the generator and the runtime resolver.)
-
-> This package is currently `"private": true` / `0.0.0` while the API surface settles. Clear
-> `private` and set a real version (the generator's `--version`/`--update-root` does the latter)
-> before the first publish.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rindle/cli",
-  "version": "0.4.3",
+  "version": "0.4.4",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",
@@ -89,12 +89,12 @@
     "typescript": "^5.7.0"
   },
   "optionalDependencies": {
-    "@rindle/cli-darwin-arm64": "0.4.3",
-    "@rindle/cli-darwin-x64": "0.4.3",
-    "@rindle/cli-linux-arm64-gnu": "0.4.3",
-    "@rindle/cli-linux-arm64-musl": "0.4.3",
-    "@rindle/cli-linux-x64-gnu": "0.4.3",
-    "@rindle/cli-linux-x64-musl": "0.4.3",
-    "@rindle/cli-win32-x64-msvc": "0.4.3"
+    "@rindle/cli-darwin-arm64": "0.4.4",
+    "@rindle/cli-darwin-x64": "0.4.4",
+    "@rindle/cli-linux-arm64-gnu": "0.4.4",
+    "@rindle/cli-linux-arm64-musl": "0.4.4",
+    "@rindle/cli-linux-x64-gnu": "0.4.4",
+    "@rindle/cli-linux-x64-musl": "0.4.4",
+    "@rindle/cli-win32-x64-msvc": "0.4.4"
   }
 }