Repository navigation
v0.21.0
·
46 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Backups, restore and moving to another server
taskspipes-backupbacks the instance up in one archive: the database (attached files included),.envwithAPP_SECRET,backup.envand the installer's Caddy files, with a manifest and checksums.--setupplans backups (none, daily or weekly), encrypts them with a passphrase (gpg, AES-256) and copies them to S3-compatible storage (AWS, Scaleway, OVHcloud, Backblaze B2, Wasabi, Cloudflare R2, MinIO…), keeping the last ones here and there.taskspipes-restoreputs a backup back — a file, the latest one, or one on the S3-compatible storage — after backing up the current state, so that a restore can be undone.taskspipes-transfer user@new-servermoves the instance to another server over SSH: same version, same secrets and settings; the old one stays intact.- The installer can start a new server from a backup —
--restore FILE, or--restore s3:latestwhen the old server is gone — and asks whether to plan backups (--backups). taskspipes-updateand one-click updates back the instance up before every update.- Administration › Backups shows the plan, the last good backup and the recent ones; administrators are told by e-mail and push notification when a backup fails, when its off-site copy fails, or when planned backups stop coming.
See Backups, restore and moving.
Upgrading
Nothing is planned by default: plan backups with sudo /opt/taskspipes/scripts/backup.sh --setup. taskspipes-update brings the new scripts; running the installer again adds the taskspipes-backup, taskspipes-restore and taskspipes-transfer commands. One-click updates work as before.