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
I would consider also the case where something goes wrong. Maybe the whole thing crashes, maybe you misconfigure something, maybe there's a power outage or something else happens and you lose the connectivity. Is there someone on site who can do anything to your hardware as you can't easily just go and figure it out by yourself?
If the answer is 'no' then I would strongy reconsider the whole approach. On a worst case scenario the system goes down before you're even back home from the trip and then your hardware is just gathering dust.
This is a good point. The answer in my case is yes, there is someone on site who is tech savvy and can help get it back up and running in the even that something goes down.
In theory that is solvable by a PiKVM,JetKVM,nankKVM, etc.
It won't help if your power supply breaks and KVM itself can malfunction too. It's of course nice to have, but it has limitations.
We are talking about a hobbyist here - if you want to have precautions against all these points OP would need to have a redundant PSU, redundant power sources with automatic failover, backup power,etc. Of course paired with redundant data connections, redundant KVM solutions, physical access management, etc.
In other words: A freaking data center.
Sure, PSUs break. Happens. But very very rarely. And everything else that is on the side of his backup device can be handled through a KVM. And tbh, if that one fails, one can usually direct a "non IT user" to simply pull the plug and put it back on.
Obviously we're talking about hobbyist level stuff and with that there's always something what can go wrong and it's not always obvious what it is. So if the 'remote end' doesn't have someone who can do at least very basic troubleshooting it can be nearly impossible to fix the setup over the phone unless you just replace the whole thing and ship whole units back and forth.
But in this particular case the remote end has someone who knows their stuff so it's taken care of, with or without a KVM. I've been thinking a similar setup with my relatives and on my case the distance isn't an issue but it's still something I'd need to bother family members with and, for me, it was simpler to get a storage box from hetzner and run backups to that instead of getting more hardware.
Maintenance is anyways something you need to consider and viable options for that vary on a case-by-case basis, so there's no 'one size fits all' solution.