Deploy an app

A runtime app is a deployable Next/V8 isolate application that runs on Comwit Cloud. You create an app inside a project, upload a build (a packaged copy of your compiled app), and Comwit makes that build live. If a new build misbehaves, you can roll back to a previous one. This page walks through the whole loop end to end.

Note

Everything here runs through the comwit CLI or the public platform API at https://api.cloud.comwit.io. You need a logged-in CLI (see Install the CLI) and a project to work in. If you are brand new, start with the Quickstart.

Create an app

An app lives inside a project. Creating one only registers the app — it does not deploy anything yet. Give it a name (for example, web):

Create an app

comwit apps create --project <projectId> --name web

The equivalent API call posts a small JSON body:

API

POST /v1/projects/{projectId}/apps        { "name": "web" }

List and inspect apps

List the apps in a project, or fetch a single one to see its current state:

List apps

comwit apps list --project <projectId>

API

GET    /v1/projects/{projectId}/apps              { "apps": [...] }
GET    /v1/projects/{projectId}/apps/{appId}
DELETE /v1/projects/{projectId}/apps/{appId}

An app resource carries these fields:

• app_id — the app’s identifier (you pass this as --app <appId>).
• name — the human-readable name you chose.
• active_build_id — the build that is currently live (empty until your first deploy).
• builds — the list of builds you have uploaded.

Note

A project with no apps yet returns 200 with { "apps": [] } — an empty list, not an error. Detail and mutation routes (the single-app GET/DELETE) still return 404 for an app that does not exist.

Deploy a build

Deploying uploads a build artifact and activates it. The simplest form points the CLI at your build output directory:

Deploy a directory

comwit deploy --project <projectId> --app <appId> --package ./dist

The --package value can be either:

• A built directory — the CLI packs it locally with tar --zstd into a temporary .tar.zst archive before uploading.
• A prebuilt .tar.zst file — upload it as-is.

Tip

If your local tar does not support zstd compression, pack the directory yourself and pass the prebuilt .tar.zst file to --package.

Optional deploy flags

You can configure hostnames, the runtime environment, and concurrency at deploy time:

Deploy with options

comwit deploy \
  --project <projectId> \
  --app <appId> \
  --package ./dist \
  --host a.example.com,b.example.com \
  --env-ref brrrd/env/app \
  --max-concurrent-requests 100

• --host a.example.com,b.example.com — bind one or more hostnames on this deploy (comma-separated).
• --env-ref <ref> — a runtime environment reference.
• --max-concurrent-requests <n> — the runtime concurrency cap.

The deploy API

The CLI calls the deployments route under the hood:

API

POST /v1/projects/{projectId}/apps/{appId}/deployments

This route does not take a JSON body

Almost every platform API route uses a JSON body, but the deployment route is the exception. The request body is the raw .tar.zst artifact sent as Content-Type: application/octet-stream. The hosts, env-ref, and concurrency options are passed as query parameters, not in the body.

A successful deploy returns:

Response

{ "app_id": "app-xxx", "build_id": "build-yyy", "hosts": [], "uploaded": true }

The new build_id is the build you just uploaded; it becomes the app’s active_build_id.

List builds and roll back

Every deploy creates a build, and Comwit keeps the history so you can return to a known-good one. List the builds for an app:

List builds

comwit apps builds --project <projectId> --app <appId>

API

GET  /v1/projects/{projectId}/apps/{appId}/builds
POST /v1/projects/{projectId}/apps/{appId}/rollbacks

A rollback re-activates a prior build without re-uploading an artifact — it flips the live build pointer back to a build you already deployed, so it is fast and does not require you to repackage anything.

Next steps

• Set runtime configuration with environment variables.
• Attach your own hostnames in Custom hostnames.
• Wire deploys into your pipeline with CI/CD.