Point at dokploy-deploy-action for rollouts

README.md

@@ -49,6 +49,7 @@ new dokploy.Domain("api", {
 - [Installing](#installing)
 - [Configuration](#configuration)
 - [Resources and data sources](#resources-and-data-sources)
+- [Deploying from CI](#deploying-from-ci)
 - [Differences from the Terraform provider](#differences-from-the-terraform-provider)
 - [Examples](#examples)
 - [Development](#development)
@@ -123,6 +124,30 @@ pulumi config set --secret dokploy:apiKey "$DOKPLOY_API_KEY"
 Data sources: `getProject`, `getProjects`, `getEnvironment`, `getApplication`,
 `getServers`.
 
+## Deploying from CI
+
+Like the Terraform provider, this one manages *configuration*, not *rollouts*.
+Creating an `Application` writes its definition; it does not build or start
+anything.
+
+[`dokploy-deploy-action`](https://github.com/maxvojtkov/dokploy-deploy-action)
+covers the other half on GitHub Actions and Gitea Actions: it triggers a
+deployment, waits for the build, and fails the job when the deployment fails.
+Export the application id from your stack and hand it over.
+
+```ts
+export const apiApplicationId = api.id;
+```
+
+```yaml
+- uses: maxvojtkov/dokploy-deploy-action@v1
+  with:
+    host: ${{ secrets.DOKPLOY_HOST }}
+    api-key: ${{ secrets.DOKPLOY_API_KEY }}
+    application-id: ${{ steps.stack.outputs.apiApplicationId }}
+    docker-image: ghcr.io/acme/api:${{ github.sha }}
+```
+
 ## Differences from the Terraform provider
 
 Everything is a mechanical translation of the Terraform provider, with three