create-feltkit 0.3.6 → 0.3.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-feltkit",
-  "version": "0.3.6",
+  "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

@@ -244,6 +244,17 @@ without their FeltDB settings.
    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.
 

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.6",
+    "@feltdb/feltkit": "0.3.7",
     "react": "19.2.0",
     "react-dom": "19.2.0"
   },

package/template/src/App.tsx

@@ -144,10 +144,12 @@ function TokenSignIn() {
   return (
     <form className="stack" onSubmit={submit}>
       <p className="muted">
-        Sign in with a session token. <code>npx feltkit vercel deploy</code> prints yours the first time it deploys. To make another, run this in your project's folder (it uses your
-        deployment's FeltDB settings from <code>.env.local</code>):
+        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.6"
+    "@feltdb/feltkit": "0.3.7"
   },
   "devDependencies": {
     "@feltdb/core": "0.16.1",