create-rindle 0.7.12 → 0.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-rindle",
-  "version": "0.7.12",
+  "version": "0.9.0",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",

package/templates/minimal/AGENTS.md

@@ -24,7 +24,7 @@ Rindle docs are served as raw markdown for LLMs: index at
 - `pnpm migrate` — one-shot `rindle migrate apply` against the unified ingress derived
   from `rindle.ncl` (the follower's `/migrate` is write-fenced). The dev loop already
   applies on boot + on every `migrations/` change.
-- `pnpm rindle:deploy` / `pnpm rindle:migrate:remote` — deploy the data tier to
+- `pnpm rindle:deploy` / `pnpm rindle:migrate:cloud` — deploy the data tier to
   Rindle Cloud (reads `rindle.ncl`, the same file `rindle up` runs locally; run
   `rindle login` once first) and push `migrations/*.sql` to the deployed master.
 

package/templates/minimal/README.md

@@ -29,9 +29,9 @@ Three tiers, same as the Rindle flagship examples:
 
 The schema lives in `migrations/*.sql`. The `@rindle/client` table schema is **generated** from it
 into `shared/schema.gen.ts` (re-exported by `shared/app-def.ts`, which layers on the relationships,
-normalization, and mutators) — so the TypeScript can't drift from the DDL. To change the schema, edit
-or add a `migrations/*.sql`; `pnpm dev` re-applies it and regenerates `shared/schema.gen.ts` on every
-change.
+normalization, and mutators) — so the TypeScript can't drift from the DDL. To change the schema,
+add a new ordered `migrations/*.sql`; `pnpm dev` applies it and regenerates `shared/schema.gen.ts`
+on every change.
 
 ## Run it
 
@@ -71,7 +71,7 @@ see the rejection path (the optimistic write snaps back + a toast).
 ```bash
 rindle login                  # once — authenticate to Rindle Cloud
 pnpm rindle:deploy            # provision / re-attach the managed app (writes .rindle/cloud.json)
-pnpm rindle:migrate:remote    # push migrations/*.sql to the deployed write-master
+pnpm rindle:migrate:cloud     # push migrations/*.sql to the deployed write-master
 ```
 
 `rindle deploy` reads `rindle.ncl` and records the binding in `.rindle/cloud.json` — commit it, so

package/templates/minimal/migrations/0001_init.sql

@@ -5,8 +5,9 @@
 -- @rindle/client TypeScript schema is GENERATED from the daemon's introspected result into
 -- shared/schema.gen.ts — so the TS can't drift from the DDL.
 --
--- To change the schema: add or edit a file in migrations/. `pnpm dev --watch` re-applies it and
--- regenerates shared/schema.gen.ts automatically; `pnpm migrate` does the same for a one-shot run.
+-- To change the schema after this file has been applied, add a NEW ordered file in migrations/.
+-- `pnpm dev` applies it and regenerates shared/schema.gen.ts automatically; `pnpm migrate` does the
+-- same for a one-shot run.
 --
 -- Column kinds map to the client schema like so: TEXT → string(), INTEGER/REAL → number(), a column
 -- declared BOOLEAN/BOOL → boolean(), JSON → json(). Column ORDER matters — the IVM engine reads it

package/templates/minimal/package.json

@@ -14,7 +14,7 @@
     "preview": "vite preview",
     "migrate": "rindle migrate apply --dir migrations",
     "rindle:deploy": "rindle deploy",
-    "rindle:migrate:remote": "rindle migrate apply --remote",
+    "rindle:migrate:cloud": "rindle migrate apply --cloud",
     "typecheck": "tsr generate && tsc --noEmit"
   },
   "dependencies": {

package/templates/minimal/rindle.ncl

@@ -9,7 +9,7 @@
 #
 #   rindle login                  # once — authenticate to Rindle Cloud
 #   rindle deploy                 # provision / re-attach the managed app (writes .rindle/cloud.json)
-#   rindle migrate apply --remote # push migrations/*.sql to the deployed write-master
+#   rindle migrate apply --cloud  # push migrations/*.sql to the deployed write-master
 #
 # `app` becomes the cloud display name and groups every component under one app in `rindle ps`.
 # `followers = 1` maps to the cloud `replicated` rung (a separate write-master + one follower,