view the rest of the comments
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!
I have a multi wan SMB router. 945mbit throughput. $60 new.
TPLink omada or Ubiquiti tier stuff is all you really need for small business. The redundant ISP connections cost way more, but it's still a tiny cost per month for something that can get the job done in a pinch like a hotspot.
Battery backups are only useful if you have a generator to take over the utility load imo. Not a common thing in small business unless you're leasing somewhere with generators provided for the whole building.
Redundant servers are not that hard to have. Just need proxmox. It's not as intuitive as old vmware but it's more than enough for a SMB. Some kind of storage shelf and three little servers gets you a ton of redundancy. If a tiny budget is necessary and small downtime is fine you really only need a couple of hosts that are beefy enough to run everything you need on each.
Well...no, and this is what I'm saying.
Every downstream issue you try to solve with redundancy has a doubled and duplicate cost to it's upstream. Internet links, load balancers for web services, and in this specific situation, UPS's.
Throwing more servers at a homelab with no power is just wasting money without more UPS power in the mix. You have 4 servers, and want HA for everything on your network, expect to have two of everything, including UPS units.
This is the n* sunken cost of redundancy at its core, and in your example, you're assuming this person even had a generator or whatever, but even if they did, they'd need an even BIGGER generator to run all this stuff.
That's why my points deal with solving for what they have and making it work better than, instead, immediately jumping to adding more and more and more to the stack. It's just not necessary when all they want is a graceful recovery to power loss.