creght-cli 0.1.16 → 0.1.18

package/README.md

@@ -1,8 +1,8 @@
-# Cregh CLI
+# Creght CLI
 
-Cregh CLI is a thin local bridge for syncing site code between a local directory and Cregh.
+Creght CLI is a thin local bridge for syncing site code between a local directory and Creght.
 
-The CLI can also run a local Vite preview for pulled Cregh projects. Cregh remains responsible for cloud rendering, CMS, assets, and the realtime preview environment.
+The CLI can also run a local Vite preview for pulled Creght projects. Creght remains responsible for cloud rendering, CMS, assets, and the realtime preview environment.
 
 ## Install
 
@@ -45,20 +45,20 @@ The command opens a browser authorization page. After authorization succeeds, th
 ~/Library/Application Support/creght/config.json
 ```
 
-The config file contains the API host and CLI token.
+The config file contains the current API host and CLI tokens. Tokens are stored per API host, so logging in to `https://creght.cn`, `https://creght.com`, or a local backend does not overwrite the other hosts' login state.
 
 When `--web` is omitted, the CLI uses `CREGHT_WEB_HOST` if set. For local API hosts such as `localhost` or `127.0.0.1`, it defaults to `http://localhost:5173`.
 For production, the default API host and default web host are both `https://creght.cn`.
 
 ## Logout
 
-Remove the saved CLI config:
+Remove the saved CLI login for the current API host:
 
 ```bash
 creght logout
 ```
 
-This clears the saved token and any saved API host. The next command will use the production default unless you set `CREGHT_API_HOST`.
+When `CREGHT_API_HOST` is set, `logout` removes only that host's token. Other saved hosts remain logged in. If the last saved token is removed, the config file is deleted.
 
 ## List Projects
 
@@ -102,9 +102,9 @@ creght project create --name="My Project" --from_id=<project_id>
 creght project create --name="My Project" --tpl_id=<template_id>
 ```
 
-## Pull Site Code
+## Pull Site Workspace
 
-Download the current remote site files into a local directory:
+Download the current remote site workspace into a local directory:
 
 ```bash
 creght pull --site_id=<project_id>/<site_id> --dir=./mysite
@@ -116,16 +116,36 @@ For local development:
 CREGHT_API_HOST=http://localhost:8433 creght pull --site_id=<project_id>/<site_id> --dir=./mysite
 ```
 
-The command writes remote files such as `/page/...`, `/component/...`, and `creght.config.ts` into the target directory.
+The command writes a file-based workspace:
+
+```text
+mysite/
+  AGENTS.md
+  frontend/
+    page/...
+    component/...
+    talizen.config.ts
+  backend/
+    func/
+      booking.ts
+      profile/settings.ts
+```
+
+Remote frontend files such as `/page/...`, `/component/...`, and
+`talizen.config.ts` are written under `frontend/`. Project Func code is written
+under `backend/func/`; for example Func key `booking` maps to
+`backend/func/booking.ts`, and `profile/settings` maps to
+`backend/func/profile/settings.ts`.
 
 ## Local Vite Preview
 
-Cregh projects pulled by the CLI usually do not have their own `package.json`
+Creght projects pulled by the CLI usually do not have their own `package.json`
 or `node_modules`. The local preview plugin therefore uses Vite only for local
 file serving and TSX transpilation; third-party packages continue to resolve
-through the Cregh import map, matching the Web editor preview model. In
-`creght dev`, the CLI loads the platform import map from server system info and
-passes it to the Vite plugin; the plugin's local map is only a fallback.
+through the Creght import map, matching the Web editor preview model. In
+`creght dev`, the CLI serves the `frontend/` directory when present, loads the
+platform import map from server system info, and passes it to the Vite plugin;
+the plugin's local map is only a fallback.
 
 Install Vite in the local project folder:
 
@@ -167,7 +187,7 @@ module after local file changes without a full page reload.
 
 ## Push Local Changes
 
-Push the current local directory snapshot to Cregh and exit:
+Push the current local directory snapshot to Creght and exit:
 
 ```bash
 creght push --site_id=<project_id>/<site_id> --dir=./mysite
@@ -179,8 +199,15 @@ For local development:
 CREGHT_API_HOST=http://localhost:8433 creght push --site_id=<project_id>/<site_id> --dir=./mysite
 ```
 
-The CLI scans the local directory and calls the existing Cregh `site_action`
-API to create or update remote files.
+The CLI scans the local workspace and diffs both frontend files and Func files:
+
+- `frontend/**` is synced to Creght site files.
+- `backend/func/**/*.ts` is synced to project Func records.
+
+Creating, editing, renaming, or deleting files under `backend/func/` creates,
+updates, renames, or deletes Func records through the backend API. Func CRUD is
+intentionally file-based; the CLI does not expose manual Func management
+commands.
 
 ## Sync Local Changes
 
@@ -197,13 +224,13 @@ CREGHT_API_HOST=http://localhost:8433 creght sync --site_id=<project_id>/<site_i
 ```
 
 `sync` first pushes the current local snapshot, then keeps running and
-automatically listens for local file changes. When a file is changed locally,
-the CLI calls the existing Cregh `site_action` API and updates the remote site
-in realtime. The command also prints the remote preview URL when available.
+automatically listens for local file changes. When a frontend or Func file is
+changed locally, the CLI updates the corresponding remote resource in realtime.
+The command also prints the remote preview URL when available.
 
 ## Local Web Editor Bidirectional Sync
 
-Run local files and the online Cregh editor against the same cloud realtime
+Run local files and the online Creght editor against the same cloud realtime
 files:
 
 ```bash
@@ -217,7 +244,7 @@ CREGHT_API_HOST=http://localhost:8433 creght dev --web=http://localhost:5173 --s
 ```
 
 The command prints the online Web editor URL, pushes local file changes to
-Cregh, and listens to the existing WebSocket collaboration channel so editor
+Creght, and listens to the existing WebSocket collaboration channel so editor
 changes are written back to the local directory. MVP conflict handling is last
 write wins.
 
@@ -317,6 +344,7 @@ List, get, create, update, and delete content entries:
 ```bash
 creght content list --site_id=<project_id>/<site_id> --collection=blogs
 creght content get --site_id=<project_id>/<site_id> --collection=blogs --slug=hello-world
+creght content get --site_id=<project_id>/<site_id> --collection=blogs --slug=hello-world --out=./content.json
 creght content create --site_id=<project_id>/<site_id> --collection=blogs --data=./content.json --slug=hello-world
 creght content update --site_id=<project_id>/<site_id> --collection=blogs --id=<content_id> --data=./content.json
 creght content delete --site_id=<project_id>/<site_id> --collection=blogs --id=<content_id>
@@ -371,9 +399,86 @@ creght form submit --site_id=<project_id>/<site_id> --key=contact-form --data=./
 
 After creating or changing CMS collections or forms, run `creght pull` again to refresh generated files such as `/types/cms.d.ts` and `/types/form.d.ts` before writing code that imports those types.
 
+## Manage Backend Tables
+
+Project JSON tables provide persistent data for Creght/Talizen Func code through
+`ctx.db.*`.
+
+```bash
+creght table list --site_id=<project_id>/<site_id>
+creght table create --site_id=<project_id>/<site_id> --key=appointments --name="Appointments" --schema=./appointments.schema.json
+creght table get --site_id=<project_id>/<site_id> --key=appointments
+creght table update --site_id=<project_id>/<site_id> --key=appointments --schema=./appointments.schema.json
+creght table delete --site_id=<project_id>/<site_id> --key=appointments
+```
+
+Manage seed or operational records:
+
+```bash
+creght table record list --site_id=<project_id>/<site_id> --table=appointments
+creght table record list --site_id=<project_id>/<site_id> --table=appointments --where=./where.json
+creght table record get --site_id=<project_id>/<site_id> --table=appointments --id=<record_id> --out=./record.json
+creght table record create --site_id=<project_id>/<site_id> --table=appointments --data=./record.json
+creght table record update --site_id=<project_id>/<site_id> --table=appointments --id=<record_id> --data=./patch.json
+creght table record delete --site_id=<project_id>/<site_id> --table=appointments --id=<record_id>
+```
+
+`record update` sends a patch body to the backend. Existing fields are merged,
+and a `null` field value removes that field.
+
+## Func Backend Code As Files
+
+Func is for small project-level backend workflows such as bookings, RSVP,
+availability checks, protected status updates, and JSON-table reads/writes.
+Func keys are extensionless project paths like `booking` or
+`profile/settings`.
+
+The normal workflow is file-based:
+
+1. Run `creght pull --site_id=<project_id>/<site_id> --dir=./mysite`.
+2. Edit or create files under `./mysite/backend/func/`.
+3. Run `creght push --site_id=<project_id>/<site_id> --dir=./mysite`, or keep
+   `creght sync` / `creght dev` running.
+
+Examples:
+
+- `backend/func/booking.ts` -> Func key `booking`
+- `backend/func/profile/settings.ts` -> Func key `profile/settings`
+
+Deleting a local Func file deletes the remote Func on the next push/sync.
+Renaming a local Func file is treated as delete old key + create new key.
+
+Func files should use ESM exports and the `(input, ctx)` signature:
+
+```ts
+export function create(input, ctx) {
+  return ctx.db.insert("appointments", input)
+}
+```
+
+Page and component code should call Func through the `talizen/func` SDK:
+
+```ts
+import { invoke } from "talizen/func"
+
+await invoke("booking.create", input)
+```
+
+Use `talizen/auth` for login, registration, logout, current-user state, and
+OAuth. Do not implement passwords, sessions, or OAuth callbacks in Func.
+
+Use `creght func run` to self-test a Func method with sample input:
+
+```bash
+creght func run --site_id=<project_id>/<site_id> --key=booking.create --input=./input.json
+```
+
+The CLI intentionally does not expose `creght func list/get/create/update/delete`.
+Use `backend/func` files for Func CRUD, and `creght func run` only for self-tests.
+
 ## Upload Assets
 
-Upload a local file through the Cregh site asset flow:
+Upload a local file through the Creght site asset flow:
 
 ```bash
 creght upload --site_id=<project_id>/<site_id> --file=./image.png
@@ -381,7 +486,7 @@ creght upload --site_id=<project_id>/<site_id> --file=./image.png
 
 The command prints the public file URL by default. Use `--json` to inspect the
 full upload metadata, including `site_path`, a stable `/_assets/...` path that
-can be used from Cregh site code:
+can be used from Creght site code:
 
 ```bash
 creght upload --site_id=<project_id>/<site_id> --file=./image.png --json
@@ -398,7 +503,7 @@ creght upload --site_id=<project_id>/<site_id> --file=./image.png --name=hero.pn
 The current MVP push/sync mode is one-way:
 
 ```text
-local directory -> Cregh remote site
+local directory -> Creght remote site
 ```
 
 `push` fetches the remote file list to build the local path to remote file id
@@ -418,12 +523,12 @@ source of truth.
 
 ## Commands
 
-Cregh CLI is a local bridge for Cregh site code. It can authenticate with
-Cregh, list projects and sites, pull remote site files into a local directory,
-push local files back to Cregh, watch local files for realtime sync, open the
+Creght CLI is a local bridge for Creght site code. It can authenticate with
+Creght, list projects and sites, pull remote site files into a local directory,
+push local files back to Creght, watch local files for realtime sync, open the
 remote preview, and publish a site.
 
-The CLI commands still use the Cregh backend and web app for the canonical
+The CLI commands still use the Creght backend and web app for the canonical
 preview. The Vite plugin is a local development helper and intentionally does
 not implement full production SSR.
 
@@ -443,17 +548,20 @@ creght content list --site_id=<project_id>/<site_id> --collection=<key>
 creght content create --site_id=<project_id>/<site_id> --collection=<key> --data=./content.json
 creght form list --site_id=<project_id>/<site_id>
 creght form create --site_id=<project_id>/<site_id> --key=<key> --name=<name> --schema=./schema.json
+creght table list --site_id=<project_id>/<site_id>
+creght table record create --site_id=<project_id>/<site_id> --table=<key> --data=./record.json
+creght func run --site_id=<project_id>/<site_id> --key=<key.method> --input=./input.json
 creght upload --site_id=<project_id>/<site_id> --file=./image.png
 creght version
 ```
 
 Command meanings:
 
-- `login`: Authenticate this machine with Cregh and save a CLI token.
-- `logout`: Remove the saved CLI token and API host configuration.
+- `login`: Authenticate this machine with Creght and save a CLI token for the current API host.
+- `logout`: Remove the saved CLI login for the current API host.
 - `project`: List available projects and sites. Use `project_id/site_id` with site commands. Also supports `project create`.
-- `pull`: Download the current remote site files into a local directory.
-- `push`: Push the current local directory snapshot to the remote site.
+- `pull`: Download frontend files and Func files into a local workspace.
+- `push`: Push the current local workspace snapshot to the remote site/project.
 - `sync`: Watch mode; push the current snapshot, then keep listening for local changes.
 - `dev`: Bidirectionally sync local files with cloud realtime files and the online Web editor.
 - `preview`: Open the remote preview URL for a site in the browser.
@@ -461,7 +569,9 @@ Command meanings:
 - `cms`: Manage CMS collections.
 - `content`: Manage CMS content entries.
 - `form`: Manage forms and form submissions.
-- `upload`: Upload a local file as a Cregh site asset and print its URL.
+- `table`: Manage project JSON tables and records used by Func.
+- `func`: Run project Func backend code with sample input. Func CRUD is handled through `backend/func` file sync.
+- `upload`: Upload a local file as a Creght site asset and print its URL.
 - `version`: Print the installed CLI version.
 
 ## Release

package/bin/creght.js

@@ -15,7 +15,7 @@ const result = spawnSync(binary, process.argv.slice(2), {
 if (result.error) {
   if (result.error.code === "ENOENT") {
     console.error(
-      "Cregh CLI binary is missing. Reinstall creght-cli and try again.",
+      "Creght CLI binary is missing. Reinstall creght-cli and try again.",
     );
   } else {
     console.error(result.error.message);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "creght-cli",
-  "version": "0.1.16",
-  "description": "Cregh CLI for syncing local site code with Cregh.",
+  "version": "0.1.18",
+  "description": "Creght CLI for syncing local site code with Creght.",
   "license": "MIT",
   "homepage": "https://github.com/creght-dev/creght-cli#readme",
   "repository": {

package/scripts/install.js

@@ -12,7 +12,7 @@ const checkOnly = process.argv.includes("--check");
 
 if (checkOnly) {
   const exists = fs.existsSync(binary);
-  console.log(`Cregh CLI binary path for this platform: ${binary}`);
+  console.log(`Creght CLI binary path for this platform: ${binary}`);
   if (!exists) {
     console.log("Binary is not present in this local checkout. CI adds release binaries before npm publish.");
   }
@@ -21,7 +21,7 @@ if (checkOnly) {
 
 if (!fs.existsSync(binary)) {
   console.error(
-    `Cregh CLI binary is missing for ${platform}-${arch}. Reinstall creght-cli and try again.`,
+    `Creght CLI binary is missing for ${platform}-${arch}. Reinstall creght-cli and try again.`,
   );
   process.exit(1);
 }

package/vite/index.d.ts

@@ -1,12 +1,12 @@
 import type { Plugin } from 'vite'
 
-export type CreghVitePluginOptions = {
+export type CreghtVitePluginOptions = {
   /**
-   * Local Cregh project root. Defaults to Vite's root.
+   * Local Creght project root. Defaults to Vite's root.
    */
   root?: string
   /**
-   * Cregh API host used by the local /api proxy at runtime.
+   * Creght API host used by the local /api proxy at runtime.
    */
   apiHost?: string
   /**
@@ -24,5 +24,5 @@ export type CreghVitePluginOptions = {
   importMap?: Record<string, string>
 }
 
-export declare function creght(options?: CreghVitePluginOptions): Plugin
+export declare function creght(options?: CreghtVitePluginOptions): Plugin
 export default creght

package/vite/index.js

@@ -77,7 +77,7 @@ const contentTypeForPath = (file) => {
 const normalizeProjectPath = (value) => {
   const out = path.posix.normalize('/' + value.replaceAll(path.sep, '/').replace(/^\/+/, ''))
   if (out.startsWith('/../')) {
-    throw new Error(`unsafe Cregh path: ${value}`)
+    throw new Error(`unsafe Creght path: ${value}`)
   }
   return out
 }
@@ -109,7 +109,7 @@ async function resolveFile(projectRoot, projectPath) {
     }
   }
 
-  throw new Error(`Cregh module not found: ${projectPath}`)
+  throw new Error(`Creght module not found: ${projectPath}`)
 }
 
 async function readSiteConfig(projectRoot) {
@@ -338,7 +338,7 @@ async function renderPage() {
   let props = {};
 
   if (!Page) {
-    throw new Error('Cregh page has no default export: ${entryFile}');
+    throw new Error('Creght page has no default export: ${entryFile}');
   }
 
   if (typeof pageModule.getServerSideProps === 'function') {
@@ -367,7 +367,7 @@ hot.on('creght:update', () => {
 async function renderHtml(projectRoot, pathname, options) {
   const routes = await listPages(projectRoot)
   if (routes.length === 0) {
-    return `<!doctype html><div style="font:14px system-ui;padding:24px">No Cregh pages found in <code>/page</code>.</div>`
+    return `<!doctype html><div style="font:14px system-ui;padding:24px">No Creght pages found in <code>/page</code>.</div>`
   }
 
   const matched = matchRoute(routes, pathname)
@@ -380,7 +380,7 @@ async function renderHtml(projectRoot, pathname, options) {
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title>${escapeHtml(matched.route === '/' ? 'Cregh' : matched.route)}</title>
+  <title>${escapeHtml(matched.route === '/' ? 'Creght' : matched.route)}</title>
   <script type="importmap">${jsonScript({ imports })}</script>
   <script type="module" src="/@vite/client"></script>
   <style type="text/tailwindcss">${indexCss}</style>
@@ -408,7 +408,7 @@ export function creght(options = {}) {
     },
     configureServer(server) {
       const hmrTimers = new Map()
-      const sendCreghUpdate = (file) => {
+      const sendCreghtUpdate = (file) => {
         if (!file.startsWith(projectRoot)) return
 
         const projectPath = normalizeProjectPath(path.relative(projectRoot, file))
@@ -429,9 +429,9 @@ export function creght(options = {}) {
       }
 
       server.watcher.add(path.join(projectRoot, '**/*'))
-      server.watcher.on('change', sendCreghUpdate)
-      server.watcher.on('add', sendCreghUpdate)
-      server.watcher.on('unlink', sendCreghUpdate)
+      server.watcher.on('change', sendCreghtUpdate)
+      server.watcher.on('add', sendCreghtUpdate)
+      server.watcher.on('unlink', sendCreghtUpdate)
 
       server.middlewares.use(async (req, res, next) => {
         try {