Good morning Fedi friends!
This is what I learned on day 7 of posting from my #GoToSocial account:
GtS caches content by others (aka media that appears on one's feed). This is the reason why my weekly backup has ballooned from 280 MB on Dec 30 to 7.7 GB on January 6.
I posted about this on my Mastodon account and @mario explained the cache issue in this reply: https://hachyderm.io/@mario/113782715282062429 (THANK YOU Mario!)
So what did I do? Easy!
I logged onto my #YunoHost admin panel → Applications → GoToSocial → Config Panel
and I changed the caching length from 7 days (default) to 2 days... which means that at midnight tonight my GtS cache will be cleared of content older than 2 days.
Explanation from GtS: When remote media is removed from the cache, it is deleted from storage but the database entries for the media are kept so that it can be fetched again if requested by a user. If this is set to 0, then media from remote instances will be cached indefinitely.
I hope this helps someone else! (esp. a fellow newbie)
#selfhosting #MySoCalledSudoLife
@elena @mario Keeping the cache under control is vital, but another thing you can do to avoid worring so much about those files is by offloading tem to an S3 compatible storage.
Attachments in my opinion are not that important so if they get lost for whateve reason (moving to a different S3 provider, or simply not backing them up) is fine for me. The DB on the other hand IS important to me. You can even let GtS proxy file requests.
I've used Backblaze's B2 for a long time and so far no complains at all. I use it for my NAS offsite backup and now also to store all my GtS attachments.
Edited 151d ago