Deployment Workflow
Learn how Jamdesk automates deployment via GitHub pushes or CLI, plus status tracking, manual rebuilds, build logs, and rollbacks.
Push to your connected GitHub branch. Your docs go live within minutes.
CLI Deploy
Deploy from the terminal without pushing to GitHub. Use it for quick iterations, testing changes, or projects not connected to a repo.
jamdesk login # First time only
jamdesk deployThe CLI packages and uploads your files. It shows build progress live. Use --detach to queue the build and exit immediately.
The Workflow
Edit your MDX files and preview with jamdesk dev.
Commit and push to your connected branch:
git add .
git commit -m "Update authentication docs"
git pushJamdesk detects your push and builds your docs. It deploys them to the CDN. Most sites build in 30-90 seconds.
Deployment Status
Check status in the dashboard under Deployments:
| Status | Meaning |
|---|---|
| Building | Build in progress |
| Deployed | Live at your domain |
| Failed | Build error - check logs |
| Queued | Waiting for previous build |
Manual Rebuild
Trigger a rebuild without pushing:
- Go to Settings in your project
- Click Rebuild
Use this after you update environment variables or to fix a stuck build.
Build Logs
Open Deployments, click a deployment, and read the logs. Common errors:
- Invalid MDX syntax
- Missing images
- Broken internal links
- Configuration errors
Rollbacks
- Go to Deployments
- Find the deployment to restore
- Click Rollback
The previous version goes live immediately.