Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swap out pictshare for pict-rs #806

Closed
dessalines opened this issue Jun 12, 2020 · 5 comments · Fixed by #807
Closed

Swap out pictshare for pict-rs #806

dessalines opened this issue Jun 12, 2020 · 5 comments · Fixed by #807
Labels
area: deployment Related to deploying Lemmy in production enhancement New feature or request
Milestone

Comments

@dessalines
Copy link
Member

Use pict-rs instead.

@dessalines dessalines added enhancement New feature or request Component: Frontend area: deployment Related to deploying Lemmy in production labels Jun 12, 2020
@dessalines dessalines added this to the 0.7.0 milestone Jun 23, 2020
@carcinocron
Copy link

Does pictrs support S3 compatible APIs? pictshare does. I couldn't find any reason for this change, otherwise this is a regression.

@dessalines
Copy link
Member Author

Pictshare had a faulty docker setup, was written in php and was full of memory leaks, to the point that it would eat up all available ram on our server.

pict-rs is a lean image server written from scratch in rust, by a dev who also works on lemmy.

We're not interested in compatibility with amazon storage, everything in lemmy is self-hosted.

@carcinocron
Copy link

"S3 compatible" means it can use a large range of providers such as GCP, B2, digital ocean, wasabi, etc. which a lot of potential server admins would prefer, especially for long-term accumulation of images.

@gellenburg
Copy link

gellenburg commented May 8, 2022

Sorry for bumping this but I just came across this looking for info on S3 storage in Lemmy before opening up a separate issue/ feature request. :-)

We're not interested in compatibility with amazon storage, everything in lemmy is self-hosted.

I'd just like to add that having S3 compatible storage is a must in 2022. Mastodon, Pleroma, Pixelfed, and I even believe PeerTube allow media to be stored on an off-site S3 compatible storage provider. I use Linode Object Storage. But Hetzner has their own S3 compatible Block Storage. OVH. Vultr too.

Having this support saves costs on hosting (block storage is usually MUCH cheaper than increasing the local storage on a VPS). Otherwise then you need to constantly increase the disk storage on your VPS.

If you're not going to support external storage there needs to be a way then to prevent any media then from being stored on Lemmy and force users to upload their media another way.

@Nutomic
Copy link
Member

Nutomic commented May 10, 2022

Image storage is completely handled by pict-rs. It looks like there is already support for object storage, you should give it a try.

https://git.asonix.dog/asonix/pict-rs/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: deployment Related to deploying Lemmy in production enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants