@pplethai/cli 0.1.0 → 0.2.1

package/dist/deps.js

@@ -3,7 +3,7 @@ import path from "node:path";
 import { fileURLToPath } from "node:url";
 export const DEFAULT_CONFIG = {
     apiBase: "https://api.ppleth.ai",
-    ssoBase: "https://sso.peoplesparty.or.th",
+    ssoBase: "https://id.peoplesparty.or.th",
     clientId: "382216793067947795",
     repoBase: "https://github.com",
     registryBase: "https://registry.npmjs.org",

package/dist/device-flow.js

@@ -18,17 +18,24 @@ function form(fields) {
         body: new URLSearchParams(fields).toString(),
     };
 }
-const UNREACHABLE = new CliError("Couldn't reach PPLE ID to sign you in.", "Check your internet connection and try `pple auth login` again.");
+/**
+ * Name the host we failed to reach. "Check your internet connection" sends a
+ * Builder to their wifi when the real fault is a bad `ssoBase` — the host it
+ * couldn't reach is the one fact that tells the two apart.
+ */
+function unreachable(ssoBase) {
+    return new CliError(`Couldn't reach PPLE ID (${ssoBase}) to sign you in.`, "Check your internet connection and try `pple auth login` again.");
+}
 export async function requestDeviceCode(deps) {
     const { ssoBase, clientId } = deps.config;
     const res = await deps
         .fetch(`${ssoBase}${DEVICE_AUTHORIZATION_PATH}`, form({ client_id: clientId, scope: SCOPES }))
         .catch(() => null);
     if (!res || !res.ok)
-        throw UNREACHABLE;
+        throw unreachable(ssoBase);
     const body = (await res.json().catch(() => ({})));
     if (!body.device_code || !body.user_code || !body.verification_uri) {
-        throw UNREACHABLE;
+        throw unreachable(ssoBase);
     }
     return {
         deviceCode: body.device_code,
@@ -59,7 +66,7 @@ export async function awaitToken(deps, device) {
         }))
             .catch(() => null);
         if (!res)
-            throw UNREACHABLE;
+            throw unreachable(ssoBase);
         const body = (await res.json().catch(() => ({})));
         if (res.ok && body.access_token)
             return toTokenSet(deps, body);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pplethai/cli",
-  "version": "0.1.0",
+  "version": "0.2.1",
   "type": "module",
   "repository": {
     "type": "git",
@@ -32,4 +32,4 @@
   "engines": {
     "node": ">=22"
   }
-}
+}

package/templates/golden-path/.env.example

@@ -2,7 +2,7 @@
 # These are the app's PPLE ID OIDC client details, used by the mini-app SDK
 # when running inside PPLE Today. They are public values, safe to ship.
 # The platform injects them at deploy time; copy to `.env` to set locally.
-VITE_OAUTH_URL="https://sso.peoplesparty.or.th"
+VITE_OAUTH_URL="https://id.peoplesparty.or.th"
 VITE_OAUTH_CLIENT_ID=""
 # Defaults to the app's own origin if unset.
 # VITE_OAUTH_REDIRECT_URI=""

package/templates/golden-path/CLAUDE.md

@@ -44,7 +44,9 @@ which attach the PPLE ID bearer token. Same origin, so paths are relative
 - **Mobile-first.** The app runs in a phone-sized WebView. Use the design
   system's components and the layout classes in `web/app.css`.
 - **Add a DB table** by writing a new `migrations/000N_*.sql` (never edit an
-  applied migration) and running `npm run db:migrate:local`.
+  applied migration) and running `npm run db:migrate:local`. The platform
+  applies `migrations/` to the live database on every deploy, so shipping the
+  file is all a deploy needs — there is no remote migrate command to run.
 
 ## Before you finish
 

package/templates/golden-path/README.md

@@ -51,7 +51,8 @@ PPLE Today, it signs the real user in via the mini-app SDK.
 ## Making it yours
 
 - **Add a table:** create `migrations/0002_*.sql`, run `npm run db:migrate:local`,
-  add queries in `src/db.ts`.
+  add queries in `src/db.ts`. Deploying applies it to the live database for you
+  — never edit a migration that has already shipped, add another one.
 - **Add an API route:** add it under `/api` in `src/index.ts`.
 - **Change the UI:** edit `web/App.tsx` using `@pplethai/components`.
 - **Send notifications:** the platform provisions `NOTIFY_API_KEY`; the helper

package/templates/golden-path/migrations/0001_init.sql

@@ -1,6 +1,7 @@
 -- The example table behind the D1 read/write demo. Replace it with your own
--- schema: add a new file (0002_add_something.sql, …) and apply it with
--- `npm run db:migrate:local` (local) or `npm run db:migrate:remote` (deployed).
+-- schema: add a new file (0002_add_something.sql, …) and apply it locally with
+-- `npm run db:migrate:local`. Deployed databases migrate themselves — the
+-- platform applies everything in this directory on each deploy.
 CREATE TABLE notes (
   id INTEGER PRIMARY KEY AUTOINCREMENT,
   body TEXT NOT NULL,

package/templates/golden-path/package.json

@@ -11,7 +11,6 @@
     "test": "vitest run",
     "test:watch": "vitest",
     "db:migrate:local": "wrangler d1 migrations apply DB --local",
-    "db:migrate:remote": "wrangler d1 migrations apply DB --remote",
     "deploy": "vite build && wrangler deploy"
   },
   "dependencies": {

package/templates/golden-path/wrangler.jsonc

@@ -39,7 +39,7 @@
 
   "vars": {
     // PPLE ID (identity). The Worker validates bearer tokens against this.
-    "SSO_BASE_URL": "https://sso.peoplesparty.or.th",
+    "SSO_BASE_URL": "https://id.peoplesparty.or.th",
     // Audience-bound notification endpoint (see src/notify.ts): the base that
     // `${NOTIFY_API_BASE}/notifications` is posted to. The platform sets the
     // real value; empty locally so notify is a no-op unless you wire it up in