Deploy Blume with Specific
Run a Blume documentation site locally and deploy its Node server with Specific.
Blume builds static documentation by default. Server features such as its MCP endpoint and Ask AI require an Astro server adapter. Specific can run the standalone server produced by Blume’s Node adapter without a platform-specific adapter.
Configure Blume
Enable server output and the Node adapter in blume.config.ts. This example
also enables the optional MCP endpoint at /mcp.
import { defineConfig } from "blume";
export default defineConfig({
ai: {
mcp: { enabled: true },
},
deployment: {
output: "server",
adapter: "node",
site: "https://docs.example.com",
},
});
Configure Specific
Place specific.hcl at the root of the Blume project:
build "docs" {
base = "node"
command = "pnpm run build"
}
service "docs" {
build = build.docs
command = "node dist/server/entry.mjs"
endpoint {
public = true
health_check {
path = "/"
}
}
env = {
PORT = port
HOST = "0.0.0.0"
}
dev {
command = "pnpm exec blume dev --port $PORT"
env = {
PORT = port
}
}
}
The build produces Blume’s standalone Node server. Specific binds it to the assigned port, exposes it publicly, and waits for the root health check before sending traffic.
Run and deploy
Install dependencies
pnpm installRun locally
specific devOpen the docs URL printed in the terminal. Changes to Markdown, components, and configuration reload automatically.
Deploy
specific deploySpecific builds the site, starts the Node server, verifies the health check, and prints the production URL.
Blume sites that do not use MCP, Ask AI, or other request-time features can use static output instead. The Node adapter is only required for server output.