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
Separate devices provide reliability and supportability.
If your all-in-one device has issues, you can't remote in to maintain it.
Take a look at what enterprises do: redundant external interfaces, redundant services internally. You don't necessarily need all this, but it's worth considering "how do I ensure uptime and enable supportability and reliability? ".
Also, we always ask "what happens if the lone SME (Subject Matter Expert) is hit by a bus?" (You are that Lone SME).
@Onomatopoeia I think in this case redundancy could be better delivered through a degree of distribution / modularity - perhaps through keeping compontents separate (I have an issue with an application but that doesn't knock out router features) but also through chain of trust with friends and family - you can't access your device (network, power, application ) then you could access backups stored with others - But I do take the point - and discused it in another comment - that perhaps modularity is the answer (e.g. Having a battery backup component that cound support a router component and an app server component ) but perhaps I'm over thinking this anyway - I have no practical way of implementing such a solution / framework myself - perhaps I'm just provocatively discussing it so that people like #Netbox and @bananapi see the discussion and think - hmm perhaps we should have closer relationships with Openwrt or Yunohost - or encourage them to come together somehow..
Exactly, keeping components separated, especially the router.
Hardware routers "cost money because they save money" (Sorry, couldn't resist that movie quote). A purpose-built router will just run and run. I have 20 year old consumer routers that still "just work". Granted, they don't have much in the way of capability, but they do provide a stable gateway.
I then use two separate mesh network tools, on multiple systems. The likelihood of both of those failing simultaneously is low. But I still have a single failure point in the router, which I accept - I've only had a couple outright fail over 25 years, so I figure it's a low risk.
Regarding the Lone SME thing, my wife has already told me if something happens to me, all my server stuff is getting donated. I should not expect her to maintain it after I’m gone. And I don’t. That’s entirely reasonable. If it lives on after I’m gone it’ll be because the recipe thing was useful enough for others to maintain. My specific server and domain kinda don’t matter.