Hey all!
Just wanted to share that we were down for about 2.5 hours today due to space issues on our server. I moved a few things around and everything seems to be up and running.
To help with this issue, I’ve moved our image server to S3 which may alleviate some of our issues, but I think the largest chuck of space is being taken up by propagated comments from other servers and I’m not sure what to do about that. We’re currently using about 300gigs out of a 320gig VPS.
It seems the S3 image uploads are working, but as always, if something seems off, let me know!
73,
w0odl
update 04:49UTC Oct/09/25: Currently migrating all of our image data to S3 so we don’t have any more broken photos
update 06:26UTC Oct/09/25: Image migration to S3 complete. Let me know if any issues arise or something seems off!
So of course one of the issues with moving to a new object store is old local images are orphaned. I’m looking at how we might be able to migrate at least our user/community images, but this may be how it is for now. You may have to reupload your profile photo/banner. I’ll work on updating the community images. Honestly, this will help us save on storage in the future.
@BenDoubleU @w0odl presumably there’s a URL map in a config file somewhere.
@vk6flab @BenDoubleU @w0odl do you happen to know where? Lemmy docs are… sparse on this topic
don’t think there’s an option for that. looks like i’ll have to migrate all of our photos over to S3. Shouldn’t take too long(?)
@BenDoubleU apologies for not replying, I’ve been having my own space issues and I’m still working out how to manage locally.
Not sure what infrastructure you’re hosting the service itself on, but one option open to you is s3fs, mount an S3 bucket as a filesystem, compatible with files uploaded using the AWS cli.
using the aws-cli as we speak (type?) should be finished in another hour or so!
testing image uploads!
