Skip to main content

First deployment

A deployment in DeployDock is a row in the Deployment table tied to an Application, created when you create an app or call POST /applications/:id/deploy.

In this page​

Prerequisites​

  • At least one Server record (created during /auth/setup or via POST /servers).
  • Redis + worker running unless you intentionally use PANEL_DISABLE_QUEUE=1 (no real adapter execution in that mode—see below).

UI path​

  1. Open /applications.
  2. Click through /applications/new (create wizard).
  3. Submit the form — the UI calls POST /api/v1/applications, which creates a deployment and enqueues deploy when the queue is enabled.

API path​

# Obtain JWT from /auth/login first
curl -sS -X POST http://127.0.0.1:4000/api/v1/applications \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{ ... CreateApplicationDto ... }'

See Swagger for the full CreateApplicationDto schema.

Worker vs inline mode​

  • PANEL_DISABLE_QUEUE not set or 0: API injects BullMQ panel queue; apps/worker must run to process deploy jobs and invoke runtime adapters.
  • PANEL_DISABLE_QUEUE=1: queue module omitted; create/deploy calls finishDeployLocal on the API—updates statuses without running worker adapter steps.

For real adapter behavior, run the worker and use Node or PHP runtimes first (Runtime matrix).

See also Using the panel: create application.