CLI Commands

This page is the complete command reference. Each command auto-detects mountsqli.config.* from the current directory.

migrate generate

Create a migration file from schema changes.

mountsqli migrate generate [--name <n>] [--dir <path>]

Option	Effect
--name <n>	custom migration name
--dir <path>	migrations directory override

Output: Created migration: <file> (writes SQL, does not apply).

migrate apply

Run pending migrations in transactions.

mountsqli migrate apply [--dir <path>] [--dry-run]

Option	Effect
--dir <path>	migrations directory override
--dry-run	print SQL, don’t execute

Output: Applying <file> ... done per step, then Applied N migration(s).

migrate status

Show applied and pending migrations.

mountsqli migrate status

Output: lists Applied: and Pending: migration names.

dev

Run the all-in-one server: REST + storage + realtime + Studio.

mountsqli dev [--port <n>]

Option	Effect
--port <n>	port (default 3737)

Output: REST/STORE/LIVE/STUDIO on http://localhost:<port>

analyze

Health report: schema drift, index suggestions, plan warnings.

mountsqli analyze

Output: a structured report (drift vs live DB, suggested indexes, warnings).

api generate

Emit OpenAPI JSON from named QueryPlans.

mountsqli api generate [--out <path>]

Reads the output path from mountsqli.config.js or defaults to openapi.json.

init

Scaffold a mountsqli.config.ts in the current directory.

mountsqli init

Best practices

• Script migrate apply into deploys; run analyze in CI.
• Use --dry-run before applying to production.

Common mistakes

• Expecting migrate rollback (not provided — see Migrations → Rollback).
• Running dev and migrate against different databases (:memory: vs file).

Related

• Overview — command summary.
• mountsqli dev — the server in depth.