Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Yes, of course 321 all the way! I was thinking 3 copies: two in RAID, one in B2 or Hetzner. Also I could keep daily ZFS snapshots for 1 month in case I mess up something. I know, it's a bit of a waste but for me it's ok since what I waste is definitely cheaper than buying a 4 bay or making a custom build. An alternative would be using two different clouds for backups and using both HDDs for space.
Nice idea, a used pc, but I'm concerned that something could fail in <4 years if the machine is too old, used office pc those are tipically from 2015-2018, so they're already 7 years old in the best case.
Thanks for the benchmark! I think 16 GB will be more enough for me then, I don't plan on using jellyfin, only transcoding would be immich but again it's ok if these task are slow.
Im using debian btw and non zfs system, so mileage may of course vary.
"Two in RAID" only means 2 when the arrays on on different systems and the replication isn't instant. Otherwise it only protects against hardware failures and not against you fucking up (ask me how I know...).
If the arrays are on 2 separate systems in the same place, they'll protect against independent hardware failures without a common cause (a drive dies, etc), but not against common threats like fire or electrical spikes.
Also, how long does it take to return one of those systems to fully functioning with all the data of the other? This is a risk all of us seem to overlook at times.