Install and run NocoBase 3 with app-installer

This Skill installs NocoBase that is already built — nothing on the machine is developed, only run. @nocobase/app-installer puts each release under releases/<version>_<build time>/app and runs it under pm2; config.yml, app.env, storage/, backups/ and logs/ sit beside the releases and survive every upgrade. It takes one of two sources, fixed at install: --template hub, which builds the published Hub on the machine, or --archive, a deployment archive built in an application project. This Skill decides when to use it and how to act on what it reports; --help is the reference for every flag.

Run it

Every command goes through npx with the registry named, and with --json:

npx --yes --registry="${NOCOBASE_REGISTRY:-https://npm.nocobase.ai}" @nocobase/app-installer <command> … --json

NocoBase 3 publishes to https://npm.nocobase.ai, not to the public npm, so a bare npx @nocobase/app-installer answers 404. NOCOBASE_REGISTRY is set only when someone points the shell at another registry, such as an unreleased snapshot; the installer reads the same variable for the Hub template, records the registry in installer.json, and suggests commands from it. The --yes before the package is npx's own: it downloads the installer without asking. The installer's --yes, after the command, is a separate answer that only the user gives.

--json prints one document on stdout and progress on stderr. Read the document, not the exit code alone: ok, status (success, success-noop or error), result, and on failure error.code, error.message, error.suggestions (each a message and, where there is one, a run command that runs as printed) and error.details.