Deploy to other hosts

A Nimbus site builds to static files by default, so any host that serves files can run it. Astro’s deploy guides cover each host’s settings.

Prerequisites

A Nimbus site. Scaffold with --deploy other to leave out the Cloudflare files, or delete wrangler.jsonc and the deploy, predeploy and preview:cf scripts from an existing one.

Steps

Set the site address
In astro.config.ts, set site in the Nimbus config to the address readers will use. On Netlify and Vercel production builds, Nimbus reads the address from the host while site is still the placeholder.
Build
npm run build
yarn run build
pnpm run build
bun run build
Publish the output
Upload the dist/ folder to your host, or point the host’s build settings at npm run build with dist as the output directory.

Verify

Open the deployed address, then the homepage’s Markdown version at /index.md. Both load: the host is serving the HTML and the agent files.

With a server

Request rendering, the remote MCP server and Markdown at page URLs need a server. Add the adapter for your host:

npx @cloudflare/nimbus-docs add adapter-node

yarn nimbus-docs add adapter-node

pnpm nimbus-docs add adapter-node

bunx @cloudflare/nimbus-docs add adapter-node

For Netlify or Vercel, use adapter-netlify or adapter-vercel. On Node, the installer adds a start script, node ./dist/server/entry.mjs. To start a new site with a server, pass --adapter to the scaffolder.

Redirects and headers

Redirects in astro.config.ts reach every host. The old Markdown and llms.txt URLs need host rules too; see Redirects. Nimbus writes headers to _headers, which hosts other than Cloudflare and Netlify may ignore; set the discovery headers in the host’s own configuration.

Deploy from CI

The “Last updated” line and the sitemap’s dates come from git history, and most CI systems clone only the latest commit. Set fetch-depth: 0 on the checkout step in GitHub Actions, or run git fetch --unshallow, before the build.

Next steps

Serve under a path: publish at example.com/docs/.
Metadata and SEO: titles, share cards and sitemaps.