Skip to content

5-minute tutorial

Deploy your first service from a Git repo. By the end, you'll have a public URL serving real traffic, with logs and metrics flowing.

You'll need a free Dockfly account and a GitHub repo with code you want to deploy. If you don't have one, fork dockfly/example-next.

Step 1 · Create your account

Head to dockfly.app/register and sign up with GitHub. You'll land on the dashboard with one default project waiting for you.

Step 2 · Connect your GitHub repo

From the project page, click Add service → Deploy from Git. Install the Dockfly GitHub App on the repo (or the whole org), then pick the repo and branch you want to deploy.

Step 3 · Let Nixpacks figure it out

Dockfly inspects your repo and picks the right build provider. For most apps you don't need to change anything — click Deploy and watch the logs stream.

logs
12:04:01 › Detected nixpacks plan
12:04:01 › providers: node, deno (selected: node)
12:04:02 [1/3] Installing dependencies (pnpm i)
12:04:09 ✓ 184 packages installed in 7.2s
12:04:10 [2/3] Running build (pnpm build)
12:04:18 ✓ Compiled in 6.1s
12:04:19 [3/3] Packing OCI image
12:04:25 ✓ Image registry.dockfly.app/api:7c3a9f2 (38 MB)
12:04:32 [deploy] Rolling deploy to sg1-node-04
12:04:36 ✓ Health check passed (HTTP 200, 84ms)
12:04:36 ✓ Live at https://my-app.dockfly.app

Step 4 · Visit your live URL

When the deploy goes green, your service is live at a Dockfly subdomain like my-app.dockfly.app. Open it in a browser — congrats, you've shipped.

Step 5 · Push a change

Make a commit on the connected branch and push to GitHub. Dockfly detects the push, builds a new image, and rolls it out — you can watch the new deploy replace the old one with zero downtime.

Health checks must pass before traffic is shifted. If a deploy fails the check, the previous version keeps running and you'll see a clear error in the deploy log.

What's next

You have a live service. Some good next steps:

Previous

← Documentation

Next

Deploy from Git →