Bug: Backup export ZIP files are not deleted after download, causing storage bloat

[Moreiq]

When exporting a backup from Fizzy, the generated ZIP file is stored in ActiveStorage but never removed after the download completes. Over time, these ZIP files accumulate inside:

storage/production/files/

This leads to rapidly increasing disk usage and exponentially growing backup sizes.

Steps to Reproduce
Self‑host Fizzy (Kamal deployment)
Export a backup via the web UI
Check the ActiveStorage directory:

/rails/storage/production/files

Export another backup

Observe that:
A new ZIP file is created and stored
Previous ZIP files remain on disk
Each new backup ZIP becomes larger than the last

Expected Behavior
After the backup ZIP is streamed to the user:

The temporary ZIP file should be deleted
The associated ActiveStorage blob should be purged
No leftover files should remain in storage/production/files

Actual Behavior
Backup ZIPs remain permanently in ActiveStorage
They accumulate with each export
Disk usage grows indefinitely
Backup ZIPs become exponentially larger because they include previous backups stored in ActiveStorage

Impact
Self‑hosted instances run out of disk space
Backups become unnecessarily large
Storage volume grows without bound
Requires manual cleanup of ActiveStorage blobs

Environment
Fizzy version: (latest as of March 2026)
Deployment: Kamal / Docker
Storage: ActiveStorage Disk service

[Mouxy]

I wonder if this is the reason why my exports keep increasing in size, and I can't restore them.

[Moreiq]

Absolutely. I wasn't able to restore because backup was from the old ver, so had to roll back a month, deploy, restore and upgrade.

[Mouxy]

I actually raised the issue with support before checking here. I shared the link for this discussion 😊

[flavorjones]

Looks like @Mouxy opened a PR: #2707

I'll review as soon as I get a chance.

[Mouxy]

Thank you!