A 13-year-old former gaming computer, with 30TB storage in raid6 that runs *arrs, sabnzbd, and plex. Everything managed by k3s except plex.
Also, 3-node digital ocean k8s cluster which runs services that don’t need direct access to the 30TB of storage, such as: grocy, jackett, nextcloud, a SOLID server, and soon a lemmy instance :)
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…
A 13-year-old former gaming computer, with 30TB storage in raid6 that runs *arrs, sabnzbd, and plex. Everything managed by k3s except plex.
Also, 3-node digital ocean k8s cluster which runs services that don’t need direct access to the 30TB of storage, such as: grocy, jackett, nextcloud, a SOLID server, and soon a lemmy instance :)
The Lemmy instance might need access to large storage.
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?)
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…