Well, it looks like I'm going to have to shut down this instance for a while until I figure out how to get more storage. I can't keep from maxing out the storage space on my 50GB VPS and I don't think I want to use S3 for cache (sounds not so decentralized to me). The cache on this thing grows forever and there seems to be no way to clear it properly. Hopefully this github issue is resolved, otherwise I'll have to figure out a new hosting solution.

· · Web · 1 · 0 · 0

Why not delete old posts uploads, expire old posts, and FULL VACUUM the DB?


Is there documentation on how to do this or would I just manually delete the posts in the interface and then run a Postgres vacuum?

About 31 GB of the 50 GB are here:


The various tootctl commands like "tootctl media remove" don't do much anymore.


Since you are going to bring it down anyway, why not try this, use the find command and delete any file there older than say 30 days? Then restart Mastodon

find /home/mastodon/live/public/system/cache -type f -mtime +30 -exec rm -f {} \;

THen just have the users reupload avatars
Sign in to participate in the conversation

This server was setup as a means to decentralize the Bitcoin social networking community in a small way. I came from The administrator there felt that the users should create their own Mastodon instances to keep the community decentralized so I created this instance.