Git Deployments

Paste a repo URL. Get a live site.

The New Instance wizard takes a git URL, a branch and a domain, detects the right engine and runs your app in its own Docker container behind the Caddy reverse proxy, with health checks and automatic HTTPS. Three steps, zero YAML.

GitHub, GitLab & self-hosted PHP, Node.js, Python, static, Dockerfile Automatic HTTPS behind Caddy

🔒panel.acme-hosting.dev/dcms/instances/new

New Instance

1 Instance Type 2 Repository 3 Runtime & Domain

Repository URL

https://github.com/acme/storefront.gitGitHub

Access token (private repos)

●●●●●●●●●●●●access verified

Branch

main14 branches ▾

Detected engine

Node.js 22 npm run build npm start

Latest commit e41c9b7 · checkout: fix rounding on discounts

Pre-Deploy Validationrunning

✓Repository Accesspassed

✓DNS & Domainpassed

Runtime Readinesschecking

                  ✓ token can read acme/storefront
                  ✓ shop.acme.dev points at this server
                  checking runtime prerequisites...
                

BackDeploy

Engine detection

DCMS reads your repo and picks the runtime

Point it at GitHub, GitLab, GitHub Enterprise or self-hosted GitLab: the provider is auto-detected, branches are listed for picking and the latest commit is captured. Then DCMS inspects the code, chooses the engine and streams every deploy step live.

PHP 7.4 to 8.3on Apache with Composer, framework-aware for WordPress, Laravel and Symfony.
Node.js 16 to 22with automatic build and start command detection.
Python 3.10 to 3.13Django, FastAPI and Flask get their entrypoint via gunicorn or uvicorn.
Static HTML or your own Dockerfileif the repo ships one, DCMS builds exactly that.
Pre-Deploy Validationchecks Repository Access, DNS & Domain and Runtime Readiness before anything builds.

🔒panel.acme-hosting.dev/dcms/instances/storefront/deploy

              › Cloning https://github.com/acme/storefront.git (main @ e41c9b7)
              ✓ Engine detected: Node.js 22 (npm run build / npm start)
              › Building image dcms/storefront:42
                step 6/9: RUN npm run build ... done in 48s
              ✓ Container started behind Caddy
              ✓ Health check passed (200 in 180 ms)
              ✓ Live at https://shop.acme.dev with automatic HTTPS
            

🔒panel.acme-hosting.dev/dcms/instances/storefront

storefrontrunningshop.acme.dev

Restart Rebuild Pull Update from Git

Recent activity

When	Action	Result
09:41	Pull Update from Git	live in 12s
08:03	Restart (env changed)	no rebuild
Sun 23:12	Auto-restart after crash	crash-loop watch 2/5
Sun 18:30	Rebuild	image :41

Day-two operations

Restart, rebuild or pull: each does exactly one thing

Every instance is its own Docker container behind Caddy, so actions are precise and boring in the best way. You always know what will happen before you click.

Restartrecreates the container from the existing image when environment variables changed: no rebuild, back in seconds.
Rebuildruns a fresh build when dependencies or the Dockerfile change.
Pull Update from Gitis the fast path for code-only changes.
Crash-loop protectioncrashed containers auto-restart, capped at 5 restarts per 10 minutes, then suppressed with a clear reason instead of thrashing your server.

3 stepsInstance Type, Repository, Runtime & Domain: from repo URL to live site

PHP, Node, Pythonplus static HTML sites and any repo that brings its own Dockerfile

0 YAML writtenno pipelines to maintain; DCMS detects, builds and runs the container

Ship your next deploy from a URL

Install DCMS free, paste a repo URL and watch your app go live behind automatic HTTPS tonight.

$ curl -fsSL https://dcms.fra1.cdn.digitaloceanspaces.com/dcms/install.sh | bash

Read the install guide See pricing

Features

More

Paste a repo URL. Get a live site.

DCMS reads your repo and picks the runtime

Restart, rebuild or pull: each does exactly one thing

Ship your next deploy from a URL