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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
That makes a lot of sense. I already have a Synology DS920+, so there’s no additional storage hardware cost on my end. The Tiny form factor is ideal for me mainly due to footprint and low noise, but total cost and idle power are definitely things I’m weighing.
Another route I’m considering is picking up just one more Tiny instead of two, and running an external Corosync QDevice directly on the DS920+ (via a lightweight Docker container) for the tiebreaker vote. That gives me a proper 2-node quorum without the hardware cost and power draw of a third physical node. Combined with the DS920+ for shared iSCSI storage, that might actually hit the sweet spot between cost, footprint, and HA.
If you only have 2 and 1 fails, you'll need to make sure the remaining one can take on 100% of the workload. If you've already maxed one and want HA, I'd suggest adding 2 more. Otherwise you'll need to decide what services are down while you repair
Indeed. With 2 nodes I’ll need to keep enough headroom for migrations if one goes down. Both hosts should normally stay online, but failure and maintenance capacity are definitely things I need to account for.
I’m also planning to monitor the whole setup through OpsHome NOC — both Proxmox hosts, workloads, Synology storage, and related services — so I can get a centralized view from my phone or web console wherever I am.
Thanks for the reminder!