v0.1.5
What's changed
Deleting a database no longer destroys its backups. They are kept by default,
listed under the project's Backups page, and you can restore a replacement
database from one — it comes back under its original name and credentials, so
applications reconnect without any configuration change. Kept backups expire 90
days after the deletion (orphaned_backup_retention_days, or 0 to keep them
indefinitely).
⚠️ One thing to check after upgrading
This release also fixes a leak in the other direction: deleting an application
used to leave its volume-backup objects behind in your backup destination, with
nothing left recording where they were. They are now erased with the application.
Objects leaked before this release are still in your destination and have to be
removed by hand — Belune no longer has a record of their keys. If you have ever
deleted an application that had volume backups, it is worth a look at your
bucket. Installs that never used volume backups are unaffected.
Upgrading
update.sh takes a backup first, as always. This release adds migration
000064; nothing existing is rewritten, and every backup you already have keeps
reading exactly as it did before. No infra restart is needed.
Features
- api,web: let backups outlive their database, and stop leaking volume backups (#10)
Fixes
- api: stop SSE streams panicking when their subscription closes (#11)
Internal
- worker: reap orphans by label and per server (#9)
- api: resolve the container runtime through a resolver (#8)
Documentation
- mark the v0.1.5 changelog entry released
Install
curl -sSL https://raw.githubusercontent.com/weiliang79/belune/v0.1.5/scripts/install.sh \
| BELUNE_VERSION=v0.1.5 bashUpgrading an existing install: run update.sh from your install
directory. Take a backup first — 0.x minor releases may contain
breaking changes.
Full changelog: v0.1.4...v0.1.5