Skip to main content
Upgrading a self-hosted instance recreates the containers on a newer image; data survives in the Docker volumes and migrations apply themselves at boot. How you trigger it depends on how you installed. Checkout-based install (setup.sh) — one command:
An upgrade never turns deck pictures on by itself: an install made before they were on by default keeps plain blocks on its cards until ./scripts/images.sh on (it checks that the browser’s sandbox starts on the host first; see Deck images). Hostinger one-file install — there is no checkout and no update.sh. Redeploy the existing Docker Manager project from the template URL, https://deploy.slideless.antasphere.com/hostinger/docker-compose.yml, which always serves the current tested pin. Keep the project name and every named volume. The full procedure, including the snapshot to take first, is in the Hostinger guide. Data survives in the pg_data and app_data volumes. Migrations are forward-only and additive-first; the booting replica applies them exactly once under a Postgres advisory lock (concurrent replicas wait, then find nothing left to do). /readyz stays 503 until the schema is current.

Pinning versions

latest follows tagged releases. To pin, set in .env:
Tags published per release (a vX.Y.Z tag): latest, X, X.Y, X.Y.Z; every push to prod publishes next and sha-<commit> for early testing.

Rollback

Take a backup before upgrading (BACKUP_PASSPHRASE=… ./scripts/backup.sh; the script refuses to run without the passphrase, Backup and restore). Rolling the image back works while the schema is compatible (additive migrations tolerate the previous app version). After a bad upgrade:

Manual migrations (AUTO_MIGRATE=false)

Operators who gate DDL run the same image once as a one-off: