refactor: retire the images tarball backup

Images and attachments are backed up off-site, one object per file, so the tar+zstd of /images goes: its service and restore, both tasks, the trigger and restore routes, the Keep last setting, the screen's Images section, and the tests. Migration 0122 drops backup_run.tar_path and import_settings.backup_images_keep_last_n and deletes any images runs. The local database dump stays for an install with no off-site destination, and the Backups card now says plainly that images and attachments are backed up only off-site. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 22:07:44 -05:00
parent 794b04a64e
commit 14936b62dc
14 changed files with 92 additions and 393 deletions
@@ -182,7 +182,8 @@ Run it for a burst of tagging, stop it to get your card back. It deploys from

 Backups live under **Settings → Maintenance → Backups**. With nothing else set
 up, the database is dumped nightly into `./images/_backups`, which is on the
-same disk as what it protects.
+same disk as what it protects. Images and attachments are backed up only to an
+off-site destination.

 To keep a copy off the machine, set up an off-site destination on the same
 screen: any S3 bucket (Fabled Archives, MinIO, AWS) and a key that may add and