Devployer
Dashboard

Deployments

Dockerfile

Publish a container from a Dockerfile. Two paths:

  1. GitHub + Dockerfile build pack — repo has a Dockerfile; Devployer builds with Docker (JDK/PHP/Node come from the Dockerfile)
  2. Inline Dockerfile — paste Dockerfile content (no Git); create from the catalog Dockerfile item

Create and pay in Devployer first, then deploy from the dashboard or from Cursor with MCP.

Dockerfile is the only method when deploying from MCP — see Deploy with MCP. If a root Dockerfile is missing, the agent must create one for the stack before deploy.

Before you start

  • A Devployer account
  • A project with an environment
  • A Dockerfile in your repo (GitHub path) or Dockerfile content to paste (inline)
  • Cursor connected to the Devployer MCP — see MCP

1A. GitHub app with Dockerfile build pack

  1. Open your project and environment
  2. Add resource → Public GitHub or Private GitHub
  3. Select your framework
  4. Under Build pack, choose Dockerfile (before runtime versions)
  5. Set the Dockerfile path (default /Dockerfile, e.g. /src/main/docker/Dockerfile.jvm for Quarkus)
  6. Pick a plan and complete payment when asked
  7. Finish creation — leave instant deploy off if you prefer MCP later

Devployer configures HTTP port and framework runtime env automatically, without Nixpacks overrides that break Docker builds.

1B. Inline Dockerfile (no Git)

  1. Add resource → Dockerfile
  2. Enter a name, paste your Dockerfile, and set the container port
  3. Leave instant deploy off if you prefer to deploy later from Cursor
  4. Pick a plan and complete payment when asked
  5. Finish creation

2. Connect MCP (optional)

Follow the MCP guide and generate an API token under Settings → API Tokens.

3. Deploy from Cursor

  1. Connect MCP — MCP guide
  2. Ensure a root Dockerfile (the agent creates one if missing)
  3. In chat: “Deploy my app on Devployer”
  4. The agent calls deploy_resource with Dockerfile and shows the logs

Step-by-step: Deploy with MCP.

Tips

  • Container listen port should match Devployer’s exposed port (Quarkus apps use 8080)
  • Create and pay in Devployer first — MCP does not create apps or take payments
  • Prefer a multi-stage Dockerfile that matches your packaging layout (e.g. Quarkus fast-jar vs uber-jar)
  • For Nixpacks from the portal (not MCP), see Nixpacks

Quick checklist

  • App created with Dockerfile build pack (or inline Dockerfile) in Devployer
  • Plan/payment completed if required
  • Root Dockerfile exists and is pushed (if deploying from MCP)
  • MCP connected (if deploying from Cursor)
  • Public URL loads when the build finishes