Skip to content
SKE

Deployments

A deployment packages your application, pushes it to your cloud provider’s container registry, provisions infrastructure, and activates the new version. Every deployment produces an immutable container image that can be rolled back to instantly.

Deploy

Section titled “Deploy”
Terminal window
ske deploy
⠋ Building container image...
✓ Image built (42s)
⠋ Pushing image to registry...
✓ Image pushed (18s)
⠋ Uploading assets...
✓ Assets uploaded (3s)
⠋ Provisioning infrastructure...
✓ Infrastructure ready (2m 14s)
⠋ Activating...
✓ Deployed successfully (3m 17s total)


  URL: https://production-my-app.example.ske.dev

The deployment pipeline:

  1. Check Docker — verifies Docker is available locally
  2. Init — requests registry credentials from the API, syncs ske.yml configuration
  3. Build — builds a container image using your Dockerfile (auto-generated or custom)
  4. Push — pushes the image to ECR (AWS) or Artifact Registry (GCP)
  5. Upload assets — scans your public/ directory and uploads static files for CDN delivery
  6. Confirm — triggers the deployment on the API
  7. Poll — streams deployment status until it reaches a terminal state

Deployment status

Section titled “Deployment status”
Terminal window
ske status
  Deployment #42
  Type:      deploy
  Status:    succeeded
  Initiator: you@example.com
  Created:   2026-09-20 14:30:00
  Duration:  3m 17s

Listing deployments

Section titled “Listing deployments”
Terminal window
ske deploy list
  ID    TYPE        STATUS      INITIATOR          CREATED
  42    deploy      succeeded   you@example.com    2026-09-20 14:30
  41    rollback    succeeded   you@example.com    2026-09-19 09:15
  40    deploy      succeeded   ci@example.com     2026-09-18 16:00
  39    deploy      failed      you@example.com    2026-09-18 15:45

Use --limit to control how many results to show:

Terminal window
ske deploy list --limit 5

Deployment details

Section titled “Deployment details”
Terminal window
ske deploy show 42

Shows full deployment details including the build and provisioning output log.

In this section

Section titled “In this section”