I'd been wondering for a while why my Digital Ocean bill kept creeping up despite not deploying new stuff. I noticed I was using way more storage in Spaces than expected, even though I'd moved Peertube to Wasabi. Maybe I'd left some videos behind?
Uh, no. I had no idea that Mastodon didn't do media cache clearing on its own until last week. That was added to the docs in 2020 (https://github.com/mastodon/documentation/commit/4617ea900a3f84e6d4393dee2bcf8dcf39a92e5a) and I spun up this server in 2019.
1.6 TB. Took 4 days to clear 4 years of cache.
feat: add a section on periodic cleanup tasks (#816) · mastodon/documentation@4617ea9
* feat: add a section on periodic cleanup tasks I asked in Discord today about which `tootctl` tasks are good to run on a regular basis (as there are a lot of cleanup jobs). It seems that `media...GitHub
Shanie
in reply to Melissa Avery-Weir • • •Melissa Avery-Weir
in reply to Shanie • • •Michael
in reply to Shanie • • •@shanie this. My single user instance amasses about 70GB per week. Without clearing out that would be about 14 TB in 4 years, if my maths is right. 😱
@melissa
Melissa Avery-Weir
in reply to Michael • • •Michael
in reply to Melissa Avery-Weir • • •Tealk
in reply to Melissa Avery-Weir • • •https://codeberg.org/Fedimins/mastodon-maintenance-tasks
mastodon-maintenance-tasks
Codeberg.orgPiers Beckley
in reply to Melissa Avery-Weir • • •stuart
in reply to Melissa Avery-Weir • • •@Gargron might consider putting a default of say 30 days into the first install. Setting up a new server is a bit complicated/confusing if you haven't done one before.
Getting your head around everything on day 1 or even day 30 is hard when your focus is on building connections with follows, relays and maybe #FediFetcher. Otherwise it's a recipe for a storage blackhole. Given images can be re-fetched on demand it seems pretty obvious.
Might even save setting up a S3.