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
@mspencer712 On your point regarding a single device - I don't think that separate hardware necessarily provides security - Though I take your point - perhaps it could be about a compatible - modular architecture - a home server, a router, a home automation hub - that are linked together easily and well.
Agree on the issue with Open source be of the "let a thousand flowers bloom" ( i just saw someone post they have a new "templated based home server" lemmy.world/post/38362941 ) - but I think thats a strength - people try stuff out - things are more loosely coupled and rely on open standards - perhaps that's a whole philispophical discussion but I think open source and open standards would attract hardware vendors - (I'm seeing plently more Openwrt based routers on chinese marketplaces than I used to - they just don't want the overhead of having to provide their own fully featured software.
I also get the - at the moment doing it yourself requires knitting together alot of stuff - that's my point - the components are all there - its more about bringing them together and smoothing the surfaces - something that I think #Homeassistant seem to be quite good at - Perhaps what is required is that kind of organisation - where there is the prospect of picking up some funding and selling some hardware that comes with all the branding.
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.