Updates

Keep Supascale up to date with the latest features and security patches.

Check for Updates

Via Web UI

1. Go to Settings
2. Look for update notification in header
3. Or check Settings > Updates

Via API

curl https://supascale.example.com/api/v1/system/updates \
  -H "X-API-Key: your-api-key"

Response (update available):

{
  "currentVersion": "1.0.0",
  "latestVersion": "1.1.0",
  "updateAvailable": true,
  "releaseDate": "2026-01-15T00:00:00Z",
  "releaseNotes": "## What's New\n- Feature X\n- Bug fix Y",
  "downloadSize": 52428800
}

Response (up to date):

{
  "currentVersion": "1.1.0",
  "latestVersion": "1.1.0",
  "updateAvailable": false
}

Force Update Check

Bypass cache and check now:

curl -X POST https://supascale.example.com/api/v1/system/updates \
  -H "X-API-Key: your-api-key"

Or with query parameter:

curl "https://supascale.example.com/api/v1/system/updates?force=true" \
  -H "X-API-Key: your-api-key"

Download Update

Download update package before applying:

curl -X POST https://supascale.example.com/api/v1/system/updates/download \
  -H "X-API-Key: your-api-key"

Response:

{
  "success": true,
  "version": "1.1.0",
  "downloadPath": "/tmp/supascale-update-1.1.0.tar.gz",
  "checksum": "sha256:abc123..."
}

Apply Update

Apply downloaded update:

Via Web UI

1. Go to Settings > Updates
2. Click Apply Update
3. Wait for restart

Via API

curl -X POST https://supascale.example.com/api/v1/system/updates/apply \
  -H "X-API-Key: your-api-key" \
  -H "Accept: text/event-stream"

Returns Server-Sent Events with progress:

event: progress
data: {"step": "downloading", "progress": 50}

event: progress
data: {"step": "extracting", "progress": 75}

event: progress
data: {"step": "applying", "progress": 90}

event: complete
data: {"success": true, "version": "1.1.0"}

Update Process

What Happens

1. Download - Fetch update package
2. Verify - Check checksum integrity
3. Extract - Unpack update files
4. Backup - Backup current installation
5. Apply - Replace application files
6. Restart - Restart Supascale

Downtime

• Typical update: 1-2 minutes
• Application restarts automatically
• Projects continue running

Update Requirements

License

Updates require:

• Valid license
• Active update subscription
• Update token configured

Check License Status

curl https://supascale.example.com/api/v1/license/status \
  -H "X-API-Key: your-api-key"

Response:

{
  "valid": true,
  "updatesExpireAt": "2027-01-19T00:00:00Z",
  "updatesActive": true
}

Rollback

If an update causes issues:

Manual Rollback

1. Stop Supascale: pm2 stop supascale-web
2. Restore backup: Located in installation directory
3. Restart: pm2 start supascale-web

Backup Location

Updates create backups at:

/opt/supascale-web/backups/pre-update-1.0.0/

Version History

Check Current Version

curl https://supascale.example.com/api/version

Returns: 1.0.0

Changelog

View release notes at each version's release page or in the update notification.

Auto-Updates

Currently, Supascale requires manual update confirmation. Auto-updates are planned for a future release.

Notification

When updates are available:

• Dashboard shows notification
• Settings page shows update badge
• API returns updateAvailable: true

Troubleshooting

"Updates expired"

1. Check license expiration date
2. Renew your update subscription
3. Verify update token is configured

"Download failed"

1. Check internet connectivity
2. Verify server can reach update server
3. Check disk space
4. Try again later

"Update failed"

1. Check error message
2. Review Supascale logs
3. Verify file permissions
4. Try manual update

Manual Update

If automatic update fails:

# Download release manually
curl -O https://releases.supascale.com/supascale-1.1.0.tar.gz

# Stop Supascale
pm2 stop supascale-web

# Backup current version
cp -r /opt/supascale-web /opt/supascale-web.backup

# Extract update
tar -xzf supascale-1.1.0.tar.gz -C /opt/supascale-web

# Restart
pm2 start supascale-web

Best Practices

1. Test in staging - Apply updates to staging first
2. Backup before updates - Have rollback ready
3. Check release notes - Understand what's changing
4. Schedule updates - During low-traffic periods
5. Monitor after update - Watch for issues