create-feltkit 0.3.5 → 0.3.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-feltkit",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "description": "Create a FeltKit application: npm create feltkit@latest my-app (add -- --template managed for Managed FeltDB)",
   "license": "MIT",
   "type": "module",

package/template/README.md

@@ -214,33 +214,55 @@ without their FeltDB settings.
    `.feltkit/deploy/.env`, then run the same `docker compose` command. With your own FeltDB
    server (`--target self-hosted`), create a key for the app's namespace (`feltdb-server keys
    create --keys <keys.json> --name tasks --namespace tasks --scope state:read,state:write`) and
-   put `FELTDB_URL` and `FELTDB_TOKEN` in `.env`. On Vercel (`--target vercel`), follow
-   `.feltkit/deploy/DEPLOY.md`: `npx vercel link`, `npx vercel env add …` for each variable, then
-   `npx vercel deploy --prod`, all in `.feltkit/deploy`. Either container refuses to start without its
+   put `FELTDB_URL` and `FELTDB_TOKEN` in `.env`. On Vercel (`--target vercel`), create the app in
+   Managed FeltDB (`npx feltdb init-managed --contract .feltkit/deploy/feltdb.contract.json
+   --runtime-scopes minimal`, which writes `.env.local`), then run `npx feltkit vercel deploy`. It links
+   the Vercel project the first time, uploads only the settings the deployment needs, deploys, and
+   signs you in: it prints the app's URL, your session token, and a one-time link to production
+   Studio. Either container refuses to start without its
    settings, and checks the database answers, so it never keeps data on its own disk. For
    Fly.io, plain Docker, or other hosts, follow `.feltkit/deploy/DEPLOY.md`.
 
    Open <http://localhost:3000>.
 
 4. **Sign in.** Production has no development sign-in (Ada and Grace are for development).
-   Until you connect your own login, create a session token, *with the app stopped* (only one
-   process may open the state), and paste it into the app's sign-in screen:
+   Until you connect your own login, sign in with a session token pasted into the app's sign-in
+   screen. On Vercel, `npx feltkit vercel deploy` printed yours. To sign in someone else (or
+   yourself again), run this in the project's folder:
 
    ```bash
    npx feltkit session create --env production --type user --id you --role member
    ```
 
-   Run it in `.feltkit/deploy` for the Node run (or anywhere with the target's `FELTDB_*`
-   variables set: then the app may keep running, since its sessions are in FeltDB). For the one-container Docker run, use a one-off container on the same
-   volume while the app's container is stopped:
+   When the deployment's data is in FeltDB (Vercel, `--target hosted`, `--target self-hosted`), it
+   uses the deployment's settings from `.env.local` and the app keeps running; it refuses rather
+   than write anywhere else when they are missing. For the Node run, use `.feltkit/deploy` with
+   the app stopped (only one process may open its state). For the one-container Docker run, use a
+   one-off container on the same volume while the app's container is stopped:
 
    ```bash
    docker run --rm -v tasks-data:/data tasks node node_modules/@feltdb/feltkit/bin/feltkit.js session create --env production --type user --id you --role member
    ```
 
+   **On AppBoundry** (`npx feltkit build --target appboundry`, then `appboundry run tasks.app`),
+   `feltkit session create` does not apply: the artifact runs without this project or FeltKit's
+   CLI. AppBoundry's operators create users with your app's roles and issue their sessions:
+
+   ```bash
+   appboundry admin users add you --role member --state <installation>
+   appboundry admin sessions issue --user you --state <installation>
+   ```
+
+   See AppBoundry's production operations guide for bootstrapping the first operator.
+
    For real users, add `auth.authenticate` to `feltkit({ ... })` to verify requests with your
    identity provider.
 
+5. **Manage it.** On Vercel, production Studio is on (at `/_feltkit/` of your app). Run
+   `npx feltkit manage` for a one-time sign-in link, or use **Manage in production Studio** on
+   the Settings page of your local Studio (`npm run dev`), which also shows where production's data
+   is and links to the live app.
+
 **Production settings** (from your secret manager, never in the repository). With one
 container, none is required:
 

package/template/_gitignore

@@ -1,3 +1,4 @@
 node_modules/
 dist/
 .feltkit/
+*.app/

package/template/package.json

@@ -13,7 +13,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@feltdb/feltkit": "0.3.5",
+    "@feltdb/feltkit": "0.3.7",
     "react": "19.2.0",
     "react-dom": "19.2.0"
   },

package/template/src/App.tsx

@@ -144,9 +144,12 @@ function TokenSignIn() {
   return (
     <form className="stack" onSubmit={submit}>
       <p className="muted">
-        Sign in with a session token. Create one on the server (with the app stopped):
+        Sign in with a session token from whoever runs this deployment. If FeltKit deployed it, <code>npx feltkit vercel deploy</code> printed yours the first time; to make another, run
+        this in your project's folder (it uses your deployment's FeltDB settings from <code>.env.local</code>):
       </p>
       <code className="block">npx feltkit session create --env production --type user --id you --role member</code>
+      <p className="muted">If AppBoundry runs this app (from its <code>.app</code> artifact), its operator creates your user and issues your session instead:</p>
+      <code className="block">appboundry admin sessions issue --user you --state &lt;installation&gt;</code>
       <input type="password" value={token} onChange={(e) => setToken(e.target.value)} placeholder="Session token (fks_…)" aria-label="Session token" autoComplete="off" />
       <button type="submit" disabled={!token.trim()}>
         Sign in

package/template-managed/_gitignore

@@ -5,3 +5,4 @@ dist/
 .env
 .env.*
 .feltdb/
+*.app/

package/template-managed/package.json

@@ -20,7 +20,7 @@
     "deploy:fly": "node scripts/deploy-fly.mjs"
   },
   "dependencies": {
-    "@feltdb/feltkit": "0.3.5"
+    "@feltdb/feltkit": "0.3.7"
   },
   "devDependencies": {
     "@feltdb/core": "0.16.1",