this post was submitted on 18 Feb 2024
71 points (91.8% liked)

Selfhosted

40296 readers
220 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] avidamoeba@lemmy.ca 3 points 9 months ago (2 children)

The Lemmy instance might need access to large storage.

[–] Dave@lemmy.nz 3 points 9 months ago

My instance's image cache is like 230GB. Plus a bunch more for the db. Can confirm storage is needed.

(unrelated question 😶 - anyone running pictrs 0.5 on local storage happily?)

[–] synae@lemmy.sdf.org 2 points 9 months ago

Thanks for the heads up.

I plan on using digital ocean's Spaces (s3-alike) where possible and also it's intended to be a personal instance, at least to start - just for me to federate with others and subscribe to my communities. Given that, do you think it'll still use much disk (block device) storage?

Might be time to familiarize myself with DO's disk pricing...