Docker · deploy guide
Deploy your own Dockerfile on DockHive
Already have a Dockerfile? DockHive builds it as-is and runs it with HTTPS on <app>.dockhive.app. The port comes from your EXPOSE line.
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 Dockerfile needs.
- 1 Push to GitHubPush the project to a GitHub repository. No Dockerfile or deploy config needed.
- 2 Pick the repoIn the DockHive console, open App Hosting and choose the repository.
- 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.
$ curl -fsSL https://dockhive.io/install.sh | sh > irm https://dockhive.io/install.ps1 | iex $ hivepod login $ hivepod deploy 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.
$ claude mcp add dockhive -- hivepod mcp Using Claude Desktop, Cursor or Windsurf? Set up the DockHive MCP server.
04
What DockHive detects for a Dockerfile
Detection reads your files; it never runs your code. Recognised by a Dockerfile in the app directory. These are the defaults; DockHive derives the exact commands from your repository (lockfile, scripts, entry module).
- Default port
- 8080
- A repository Dockerfile always wins over framework detection: DockHive builds it as-is.
- With no EXPOSE line, the port falls back to the detected framework port, then 8080.
- Used whenever the app directory contains a Dockerfile.
- The port comes from the Dockerfile's EXPOSE line.
05
Environment variables and custom domains
Environment variables
Drone spots the variables your app reads. Set the values in the console, with --env on hivepod deploy, or through your agent. Values are write-only. Secrets and .env files are never uploaded.
Custom domains
Every app gets <app>.dockhive.app with HTTPS. To use your own domain, add it to the app and point a CNAME record at DockHive; the Let's Encrypt certificate is issued automatically.
Dockerfile on DockHive: FAQ
Which port does a Dockerfile use on DockHive?
The port comes from the EXPOSE line in your Dockerfile. Without one, DockHive falls back to the detected framework port, then 8080.
Will DockHive replace my Dockerfile?
No. When the app directory has a Dockerfile, DockHive builds it as-is and takes the port from its EXPOSE line.
How do I set environment variables for my Dockerfile?
Drone spots the variables your app needs. Set the values in the DockHive console, with hivepod deploy --env KEY=value, or from your AI agent over MCP. Secrets and .env files are never uploaded.
Does every push redeploy my Dockerfile?
Yes. After the first successful deploy Drone saves the working setup, and every push to the connected GitHub repository redeploys automatically.
More deploy guides
Ship your Dockerfile today
Start on the Free Tier. The Developer Plan is $3/month. See pricing