Backups and upgrades1.x

In-app backup and restore

Settings → Backup & Restore dumps the main and Warden databases as db.sql and warden.sql under {CONFIG_PATH}/backups/. Contents, schedule, retention, and restore steps are covered in Backup settings.

Blobs are not in the SQL dump

Mounted content depends on {CONFIG_PATH}/blobs/. Back up that directory separately if you need a full restore of WebDAV content.

PostgreSQL main database

When DATABASE_PROVIDER=postgres, back up the main database with pg_dump; see PostgreSQL.

Before upgrading

Back up the whole /config volume, including blobs/, or at least create an in-app backup and copy blobs/.

Upgrades

docker compose pull
docker compose up -d

Database migrations apply automatically on startup. Back up /config before upgrading across versions that include schema migrations. Irreversible migrations appear under Breaking Changes in the changelog; routine additive migrations are noted in the release announcement instead.

Coming from an older release or another fork? See Migration paths.

Tags: latest (current stable), lts (trails latest by a few releases), rc (release candidate), and dev (unversioned tip snapshot), plus pinned version tags — see Release channels and tags, GitHub Releases, and Changelog.

Automatic container updates

If a tool updates containers automatically, pin a known-good tag or keep the in-app backup schedule on before unsupervised upgrades.