Deployments, previews and rollbacks

When you create a project, Darmi Cloud installs a webhook on your GitHub repository. Every push to your production branch triggers a new deployment automatically. You can toggle auto-deploy or reconnect the webhook in Project → Settings → Git.

Open a pull request and Darmi Cloud builds a preview environment at <project>-pr-<number>.darmicloud.tech so you can review the change on a live URL. Closing or merging the PR tears the preview down automatically. PR previews are available on paid plans.

Every successful production deployment is kept in the project's history. If a release goes wrong, open a previous successful deployment and click Rollback — the platform rebuilds that exact commit and routes traffic to it.

Create a deploy hook in Project → Settings to get a secret URL that triggers a deployment when called — useful for CI pipelines, CMS publish events or scheduled rebuilds. Anyone with the URL can trigger a deploy, so treat it like a password.

Every deployment streams live build and runtime logs. Statuses move through queued → cloning → building → deploying → deployed (or failed). Failed deployments keep the error message and full logs for debugging — and on Pro and Team plans, the AI Build Doctor can explain the failure for you.