SolidStart

Nitroship deploys SolidStart’s Nitro-backed server bundle and client assets. The preset targets the Node-server output, not an edge or browser-only adapter.

Detection and build outputCopy Anchor Link

• Detection: @solidjs/start in package.json. Keep the project’s build script.
• Current Vite-based projects need nitro and the nitro/vite integration in their Vite configuration. A plain Vite server build without an HTTP server adapter is not enough.
• Nitroship sets NITRO_PRESET=node-server. The self-contained .output bundle starts with node server/index.mjs; .output/public goes to the CDN.
• Keep the default Nitro output layout. Custom edge adapters or different server entrypoints require a Dockerfile.

DeployCopy Anchor Link

curl -fsSL https://nitroship.co/install.sh | bash
ntro login

{
  "build": {"framework": "solidstart"},
  "compute": {"regions": ["kr-icn"]}
}

Setting build.framework skips detection and uses this preset, even if your project root has a Dockerfile. It can't be combined with build.dockerfile. Without it, Nitroship detects the build as described in How Nitroship chooses a build.

ntro apps create my-solidstart-app
ntro deploy . --prod

After installing dependencies, you can also build locally with ntro deploy . --prod --local. After deployment, open static assets and a server route at the URL printed by the CLI.

Limits and custom setupsCopy Anchor Link

Server deployments need a compute region. Your server must listen on 0.0.0.0:$PORT (default 3000). Client assets come from the CDN, and a single Node server handles all SSR and API requests; routes aren't split into separate functions the way Next.js routes are.

Nitroship does not automatically run migrations, queue workers, or schedulers. Run migrations in CI or locally; see Scheduled jobs for periodic work. Store uploads in S3 or other object storage, and configure secrets through Environment variables.

For adapters or output layouts outside this contract, use your own Dockerfile. Remove build.framework and define installation, build, and startup in the Dockerfile.