Ope (ノ*°▽°*)

Yup Yup! I’ve got it uploading objects. It seems to be an issue with fetching them. The hash is either mismatched or it’s not correctly trying to grab from the sled repo. So, I get a 500 error in store response. Not really sure how to fix it.

Safing.io Portmaster

I am using the from scratch install and on 0.18.5 and using pictrs 0.4.0 beta (or whichever build comes with the embed version)

Initially, when I set my object storage creds in the docker-compose.yml file, it seemed to work and I see in my bucket it populated some files.

But now I don’t think it is writing anything to the bucket. Any ideas? Thanks!

Thanks! And to answer your question, I always like building from source to know exactly what’s involved. Just a hobbyist thing I guess lol

Turns out, even with the from scratch install, I needed to edit the docker-compose.yml file to add the pict-rs env vars. It’s working now.

You may want to also look at offloading media with pict-rs to a object storage like an S3 API compliant bucket. Otherwise, you’ll find Lemmy soaks up lots of storage.

Seems the only caveat to doing this is that now my instance is growing about ~2GB per day lmao

Might need to find a way to prune the storage or else this won’t be financially maintainable hah

Nice, that’s a great explorer. Looks like I’ve got quite a lot of indexing to do.

Hell yea. The LCS tool is working beautifully. Thanks for that!

Seems maybe that tool is a bit different? If you have a new community, you can use that tool to submit it. Rather than the opposite I’m looking for, where it lets me find new communities I’m not yet subscribed to (directly within my homeserver search).

Ah interesting, thanks. I’ll see if I can find some. That makes sense that it relies entirely upon the users of the instance and what they search/subscribe to. So, as a single-user instance, it’d only show what I venture out to find. Hopefully, the scripts you speak of can help automate some of that.