When Beehaw was first launched our disk usage (physical space on the server) was approximately 45%.
Right now we are up to 72% and this will continue to climb over time.
At the moment, I can only see two options. Firstly, go up an additional tier with our server host which would increase the monthly hosting cost.
Secondly, figure out a way to remove old and inactive posts. Hopefully, there is a batch process for this or something similar. I’m not an expert in this area, sadly.
What are your thoughts?
At what level do we have control over the images uploaded to beehaw? I know we’ve broached this topic a few times with @dessalines but I don’t remember the outcome. Can we cap how many kb or size in pixels as a stop gap?
Is there anyone who uses our instance that can help to push for more granular control over what can be eating up disk space or can develop scripts to help us manage this? This instance (and likely others) would find scripts for removing old content with no comments, focused on the largest objects first particularly valuable. Something to proactively identify anything taking up a lot of space on the server could help too.
Follow this link to find the developer responsible for ‘pict-rs’ which handles images/thumbnails.