Manage SQRL app deployments for your projects.

This app is required to connect your repositories to DataSQRL Cloud.

No Deployment Yet

This project doesn't have a deployment yet. To start using your project, you'll need to create a deployment.

New Deployment Button

Click the "New Deployment" button above to create a deployment from the default repository branch.

Automated Deployments

Push commits to your configured deployment branch to trigger automated deployments.

Manual Deployments via GitHub

Post a comment with @datasqrl /deploy under a Pull Request to manually trigger a deployment from any branch. /deploy with nothing after it only works when exactly one project is linked to this repository; otherwise add a token. An optional token is checked against each linked project's project id (UUID), name, and deployment label. A UUID or name resolves to at most one project—duplicate names or other ambiguity require a UUID. One comment can trigger several deployments only when the token matches no id or name and matches a shared deployment label for multiple projects in the same organization; if that label also appears in another organization, use a UUID. Use double quotes if the token contains spaces, for example @datasqrl /deploy "my staging".

Deploy with extra package.json

You can attach multiple extra package.json manifests for a single deployment. They are merged after this project's configured package.json paths. In a PR comment, add each file with its own flag (do not put several paths after one flag): repeat --extra-package-json <path> as many times as you need. The "New Deployment" flow above also lets you enable "Append extra package.json" and pick multiple JSON files in the file tree when your GitHub account is linked.

Example with two extras: @datasqrl /deploy <uuid-or-name-or-label> --extra-package-json packages/package.json --extra-package-json packages/package2.json

Each path must be repo-relative and lie under this project's source folder.

---

See more at datasqrl.com.