Skip to content
CantelopBeta

Deployment

A deployment releases the Edge API and Session runtime together to the App named in cantelop.json. Sign in with cantelop login and configure your production environment before deploying.

Terminal
$ cantelop deploy
  • Complete releases: the CLI builds and uploads the API bundle and Session image, then reports provisioning progress for both components.
  • Activation: a release becomes active only after both components succeed. If either fails, the release is not activated.
  • Runtime images: use the default image or an optional Dockerfile for dependencies.
  • Build validation: cantelop deploy --dry-run runs the same build without login, uploads, or release creation.

Cancel an interrupted upload#

If an abandoned upload is blocking a new deployment, cancel it without rebuilding the image or waiting for the one-hour upload expiry:

Terminal
$ cantelop deploy cancel
# Or specify the App without a local project:
$ cantelop deploy cancel --app my-app

Cancellation releases the App's upload lock and clears the matching local retry state. If storage cleanup needs a retry, the CLI prints the exact command; new deployments can proceed in the meantime. Use --upload UPLOAD_ID to target a specific upload. Queued, provisioning, and active releases are not cancelled.

See the CLI reference for first-time App creation, command options, release history, logs, and rollback.