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
I don't understand why people want to use so many PC's rather than just run multiple VM's on a single server that has more cores.
Having multiple machines can protect against hardware failures.
If hardware fails, you have dono machines.
It's good learning, both for provisioning and for the physical (cleaning, customising, wiring, networking with multiple nics), and for multi-node clusters.
Virt is convenient, but doesn't teach you everything
I'm not sure if running multiple single SSD machines would provide much redundancy over a server with multiple PSU's and drives. Sure the CPU or mobo could fail but the downtime would be less hassle than 25 old PC's.
Of course there is a learning experience in more hardware but 25 PC's does seem slightly overkill. I can imagine 3-5 max.
I'm probably looking at this from a homelab point of view who just wants to run stuff though, not really as the hobby being "setting up the PC's themselves".