create-rindle 0.6.3 → 0.6.4

package/package.json

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

package/templates/minimal/README.md

@@ -73,8 +73,10 @@ pnpm rindle:migrate:remote    # push migrations/*.sql to the deployed write-mast
 ```
 
 `rindle deploy` reads `rindle.ncl` and records the binding in `.rindle/cloud.json` — commit it, so
-future deploys re-attach to the same app. `followers = 1` provisions the colocated pair
-(`single-backup`); raise it for read replicas (`read-scaled`). That deploys the **data tier**; the
+future deploys re-attach to the same app. `followers = 1` provisions a backed-up write-master + one
+follower (`replicated`, scales 1→N in place); raise it for more read replicas (`read-scaled`);
+`localRetention = true` provisions the one-box colocated pair (`colocated`, no streaming backup —
+no durability beyond the box). That deploys the **data tier**; the
 **web app** (this Vite/TanStack Start app) deploys to any Node host — point its `RINDLE_DAEMON_URL`
 (fleet-edge reads) + `RINDLE_REPLICATOR_URL` (writes) + their tokens (server) at the deployed data
 tier, and set `VITE_FLEET_WS` to the stable public fleet ws. These bindings are identical for one or

package/templates/minimal/rindle.ncl

@@ -12,8 +12,9 @@
 #   rindle migrate apply --remote # 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 `single-backup` rung (one box, both processes); `followers > 1`
-# maps to `read-scaled`.
+# `followers = 1` maps to the cloud `replicated` rung (a separate write-master + one follower,
+# backed up; scales 1→N in place); `followers > 1` maps to `read-scaled`. `localRetention = true`
+# maps to `colocated` (one box, both processes, no streaming backup).
 #
 # Every follower count renders a local fleet edge (the Fly-edge stand-in;
 # FOLLOWER-AFFINITY-DESIGN.md §10). `rindle exec` derives the app's read/write/ws bindings from this