Deploy by framework

Analog

Deploy Analog’s Nitro SSR output or its generated static site.

Nitroship supports Analog’s Nitro-backed Node server and its static output.

Detection and build output

  • Detection: @analogjs/platform in package.json; keep the project’s build script.
  • Server builds set BUILD_PRESET=node-server and NITRO_PRESET=node-server. The self-contained dist/analog bundle starts with node server/index.mjs; dist/analog/public is published to the CDN.
  • When a static build produces dist/analog/public but no server entrypoint, Nitroship publishes that folder without compute. This includes Analog’s static configuration (static: true, ssr: false).
  • Keep the Analog output layout; custom Nitro edge targets or other layouts require your own Dockerfile.

Deploy

Install the CLI

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

Already installed? Skip ahead. Full options, PATH setup, and updates: Install the CLI.

nitroship.json
{
  "build": {"framework": "analog"},
  "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-analog-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 setups

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.

On this page