Remix v2

Nitroship runs Remix v2’s Vite server build as one managed Node server. For React Router framework mode, use the React Router preset.

Detection and build outputCopy Anchor Link

• Detection: @remix-run/dev in package.json; use the Vite build, normally remix vite:build.
• The server runs remix-serve build/server/index.js; build/client is published to the CDN.
• Put @remix-run/serve and other runtime packages in dependencies: the bundle includes production dependencies.
• The classic Remix compiler, custom server entrypoints, and other runtime adapters are outside this preset’s Vite output contract.

DeployCopy Anchor Link

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

{
  "build": {"framework": "remix"},
  "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-remix-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.