I have a tiny little instance that's being absolutely overwhelmed after I connected it to other communities. I've run a script to give me something like 40K posts to toss off to the purge API, but somehow my disk usage is expanding while this purge is going on. My disk usage is being caused by all the media, but I'm sure how to nuke media from outside of the instance efficiently. The API calls are kind of slow. I'd rather just issue a direct command to delete the media from existence, but I haven't been able to find where the delete tokens for posts are stored to just rapid fire issue the command from within my server (and thus not have to stagger my calls to not be rate limited)
Can someone help me? I feel like there's something pretty simple I'm overlooking here.
EDIT 1:
Running some diagnostics, I learned that 10GB of my disk is media and 10GB is the activity table (Thanks @[email protected] for pointing that out to me)
I am still left wondering how to purge the 10GB of worthless media in a way that doesn't leave everything corrupted. Of course I can just navigate to where it is on disk and just deleted, but this feels like a bad idea. My attempt to just run purge API calls has been stymied by rate limiting. Congrats to lemmy for that, but really sucks for me who needs to delete a lot of files.
Nope. Because I know I'm going to be a complete purge and I know that no one has uploaded any media, I just nuked the folders after being reasonably certain nothing bad would happen. I think that I'm going to end up writing a periodic proper purge script that is going to directly talk to pict-rs and will be awful for me to do because I know fuck all about docker, so some experimentation will be necessary.