manic start

manic start runs the compiled production server produced by manic build.

Decision flow

Initializing diagram...

${build.outdir}/server.js must exist (default build.outdir is .manic → .manic/server.js).
Run manic build first if you see “Build not found”.

bun ${build.outdir}/server.js

with cwd set to the project root and env extended with:

Variable	Value
`PORT`	CLI `--port` / `-p`, else `config.server.port`, else 6070
`NETWORK`	`true` if `--network` was passed, else `false`
`NODE_ENV`	`production`

Stdout/stderr are inherited so logs appear in your terminal.

Same global parsing as manic dev:

-p, --port <number> — sets PORT for the subprocess (see CLI Overview for how this interacts with server.port in manic.config.ts).
--network — sets NETWORK=true on the subprocess.

There is no manic start --help subcommand; manic --help lists global usage.

manic build
manic start
manic start --port 8080

In package.json, scaffold templates often wire "start": "manic start" after build.