Deployments
Review the full deployment history for an app — every build, its trigger, branch, status, and logs.
The Deployments page lists every deployment that has ever been triggered for this app, in reverse-chronological order. Use it to audit release history, understand what triggered a deploy, and drill into build logs for any past deployment.
Deployment types
Skytells distinguishes between two deployment types, shown as a label on each deployment and in the app's deployment detail:
| Type | When created | URL |
|---|---|---|
| Production | Every push to the production branch (e.g. main), or a manual deploy. This is the deployment actively serving traffic. | The app's primary *.skytells.app domain — and any custom domains attached. |
| Preview | When Enable preview deployments is on and a pull request is opened, or a push lands on the preview branch. | A separate, temporary *.skytells.app URL scoped to that PR or branch. Torn down when the PR closes. |
Only one Production deployment is live at a time. Multiple Preview deployments can exist simultaneously — one per open pull request.
Preview deployments are configured in Settings → Git → Preview Deployments. See Settings for details.
Deployment list
Each row in the deployment list shows:
| Field | Description |
|---|---|
| Title / Commit message | The commit message from the triggering push, or Deploy #<id> for manual deployments. |
| Trigger | How the deployment was started: Git_push (automatic on branch push) or Manual (triggered from the Console or API). |
| Branch | The branch that was deployed (e.g. main). |
| Date | When the deployment was started. |
| Status | Current state of this deployment: Ready, Building, Failed, or Cancelled. |
The refresh button in the top-right re-fetches the list to show the latest state without requiring a full page reload.
Deployment statuses
| Status | Meaning |
|---|---|
Ready | Build succeeded and the container is running this deployment. |
Building | Build is currently in progress. |
Failed | The build or container startup failed. Open the deployment to see the error. |
Cancelled | The deployment was manually cancelled before it completed. |
Only one deployment can be the active production deployment at any time — the one currently serving traffic. Previous Ready deployments remain in the list for history and rollback reference.
Viewing deployment logs
Select any deployment row to open its detail view. The detail view shows:
- The full deployment ID (e.g.
2410de39) - The triggering commit hash
- The complete build log output:
- Install step output
- Build command output
- Container startup confirmation
- Distribution across Skytells's global edge infrastructure
Commit: 07cc47df5564944da46aec606760153fce7e0335
Deployment: #2410de39
Build succeeded
Deploying to optimal infrastructure...
✓ Deployment succeeded.
✓ Distributing your app on Skytells's global edge infrastructure...
✓ Your app is live on Skytells's global network.Redeploy from history
You can retrigger any past deployment from its detail view. This is useful for rolling back to a known-good build without having to git revert.
Redeploying a past commit uses the image from that build — it does not re-run the build from that commit's source. Environment variables at the time of redeployment are the current ones, not the ones that were active when the original deployment ran.
Related
- Logs — stream real-time build output for the current deployment.
- Settings — Git — configure the production branch and auto-deploy behavior.
- Settings — Deployment — toggle auto-deploy and cache clearing.
How is this guide?
Overview
The App Overview is the command center for a running Skytells app — showing live status, the active deployment, domains, CI/CD connection, and quick actions.
Environment
Manage build-time and runtime environment variables for a Skytells app — add, edit, and scope variables to control how your app builds and runs.