Deploy Node.js on DockHive

01

Deploy with Drone (zero config)

Drone is DockHive's AI deploy agent. It reads the repository, works out the stack, writes the Dockerfile, picks the port and health check and lists the env vars your Node.js app needs.

1. 1 Push to GitHubPush the project to a GitHub repository. No Dockerfile or deploy config needed.
2. 2 Pick the repoIn the DockHive console, open App Hosting and choose the repository.
3. 3 Deploy with DroneDrone builds it. If the build or health check fails it reads the logs, fixes the build setup and retries, then goes live on <app>.dockhive.app with HTTPS.

Drone saves the working setup, so every push to the repository redeploys automatically. How Drone works

02

Deploy from the terminal

Install the hivepod CLI, sign in once, then run hivepod deploy in the project folder. It uploads the folder (without .git, node_modules, virtualenvs or secrets) and Drone builds it.

Deploying the same folder again updates the same app. Set variables on the way with hivepod deploy --env KEY=value.

03

Deploy from your AI agent (MCP)

The CLI includes an MCP server. Add it to Claude Code, then ask your agent to "deploy this to DockHive". The agent calls the deploy tool and hands back the live URL, or Drone's summary and any missing env vars if something needs your input.

Using Claude Desktop, Cursor or Windsurf? Set up the DockHive MCP server.

04

What DockHive detects for Node.js

Detection reads your files; it never runs your code. Recognised by a package.json with a "start" script or a "main" file (when no more specific framework matches). These are the defaults; DockHive derives the exact commands from your repository (lockfile, scripts, entry module).

Default port

3000

Install

npm ci

Start

npm start

• Start: your start script, or node <entry> using package.json "main" or the first of server.js, index.js, app.js, main.js, src/server.js, src/index.js.
• Port: read from the entry file when it has a pattern like .listen(3000) or process.env.PORT || 3000; 3000 otherwise.
• Needs a package.json in the app directory.
• Node.js version: taken from "engines.node" in package.json and rounded up to 20, 22 or 24 (22 when unset).
• Package manager: pnpm when there is a pnpm-lock.yaml (or "packageManager": "pnpm@…"), Yarn when there is a yarn.lock, npm otherwise.
• Install: npm ci with a package-lock.json (npm install without one), pnpm install --frozen-lockfile, or yarn install --frozen-lockfile (--immutable on Yarn Berry).
• Build: your "build" script runs when package.json has one.
• Generated images set PORT, listen on 0.0.0.0:$PORT and run as a non-root user wherever the runtime allows. Nothing is written back to your repository.
• Monorepo? When the repository root isn't an app, DockHive looks one level down (app, web, frontend, backend, server, api, src, site, client first).

05

Environment variables and custom domains

Node.js on DockHive: FAQ