@ungic/cli

The ungic command: runs, builds and deploys an ungic Site — ungic.base.ts (the data model, rules, sign-in, admin layout, functions, apps) and ungic.config.ts (your configuration over it). Start a Site with npm create @ungic my-site.

ungic dev                run the Site for development: API, admin and apps on one port, restarted on change
ungic build              check the Site and bundle it for production into dist/
ungic start              run the production build (dist/server.mjs)
ungic migrate            write, apply and inspect migration files: plan | apply | status
ungic owner              create the Site's first owner: the admin account that invites the rest of the staff
ungic keys rotate        re-encrypt the stored secrets after a site-key rotation
ungic functions pin      follow the base's functions with your replacements
ungic adopt              turn a standalone-source export of the ungic builder into a theme project

ungic <command> --help prints a command's options. Every command reads .env in the Site's folder (variables already set win) and takes --config <file> (default ./ungic.config.ts).

• dev runs the content API (/api), the admin (/admin/, with your pages and field editors from admin/) and the apps on one port, and restarts the CMS when the config, the base, server code, a migration or .env changes. Database: DATABASE_URL, else PGlite in .ungic/pglite (--memory for a throwaway one). Safe schema changes are applied by themselves; a risky one is refused with its fix.
• build fails, with the fix, on what would fail in production — TypeScript, the config, the function contract (every mock: true function of the base replaced in ungic.config.ts), a schema change without a committed migration — then writes dist/: server.mjs (a Node server), handler.mjs (a fetch handler for serverless hosts), the apps built from theme/, your admin pages. --vercel also writes the Vercel function and vercel.json.
• start runs dist/server.mjs in production mode: only committed migration files are applied, and any other difference between the database and the schema refuses the start. Needs DATABASE_URL (or PGLITE_DIR for one instance on a persistent disk).
• migrate plan writes migrations/<NNNN>_<name>.ts from the schema change, apply applies pending files (what a production start does), status lists them.

The apps built from theme/ need @ungic/web (an optional peer: the projects the ungic builder exports list it; npm i @ungic/web otherwise).

ungic dev runs as two processes: the one you started owns the port and serves the apps built from theme/ (Vite, HMR); the CMS runs in a child on an internal port (127.0.0.1, random) that is restarted on change, and everything that is not such an app (/api, /admin, prebuilt frontends) is proxied to it.

Documentation

• CLI reference: every command and option.
• Getting started · Migrations · Deployment
• Functions and hooks (the function contract ungic build checks)
• Apps built from theme/ (server rendering, prerendered pages)
• Ungic CMS documentation.

License: Apache-2.0.