Design patterns

Submitted ⁨⁨4⁩ ⁨months⁩ ago⁩ by ⁨abeorch@lemmy.ml⁩ to ⁨selfhosted@lemmy.world⁩

Just a bit or a wandering mind on my part but one of the issues in the back of my mind is what happens to whatever self hosting I setup if something happens to me.

Ideally I’d like to be able to know that in case of emergency Id be able rely on a good friend or two to keep things going.

My thought was that would require some common design patterns/ processes and standardisation.

I also have these thoughts because eventually Id like to support other family members with self hosted services at their places. Standardising hardware, configurations etc makes that much simpler.

How have others approached this?

source

Comments

Sort:hotnew top

abeorch@lemmy.ml ⁨4⁩ ⁨days⁩ ago
So an update on this. I have started looking at yunohost.org because it standardises the installation and maintenance of a variety of common apps - HomeAssistant, LDAP, email server, mqtt, Nextcloud. i recently saw a post on Reddit about succession planning which reminded me about my own questions.

source
tofubl@discuss.tchncs.de ⁨4⁩ ⁨months⁩ ago
github.com/potatoqualitee/eol-dr

source
- Tippon@lemmy.dbzer0.com ⁨4⁩ ⁨months⁩ ago
  That’s a really good idea, thanks for the link :)
  
  source
- abeorch@lemmy.ml ⁨4⁩ ⁨months⁩ ago
  Useful I have some of this but not other bits. A bit morbid but Im interested in what the break glass mechanism would be.
  
  source
  - tofubl@discuss.tchncs.de ⁨4⁩ ⁨months⁩ ago
    It’s not my Github, but I think you’d do something like print and store in a safe place your trusted party has access to. My SO has my Keepass password stored in their password safe and theoretically knows (and hopefully will recall when the need arises) how to find my Keepass file, for example.
    
    In short, it’s trust. And then there’s the fact that they would never voluntarily touch this stuff anyway. 😅
    
    source
    -> View More Comments
helpimnotdrowning@lemmy.sdf.org ⁨4⁩ ⁨months⁩ ago
I’ve acknowledged that, while convenient, my (small) setup is still a burden that I would be asking someone to take. If your friends don’t already share your passion or knowledge for Linux/Docker/the intricacies of <whatever you may be running>, I doubt they’d be willing to take on what you leave them.

My friends had a family member who had a giant setup of Raspberry Pi’s that did Pi-hole, Home Assistant, F@H, among many other services and machines (there were like 6 Pi s!). They passed some time ago, and there’s just no one in the family who was willing to take on the responsibility to learn how to manage everything that was going on—services have been slowly degrading/going down since then.

Those who rely on your services will just go back to using Google Drive, watch-anime-free.org.ru, and pressing “Open LAN world” in the Minecraft client. I don’t think it’s okay, but if you’re out of the game, you won’t be there to object.

That is to say, if you DO have friends that are knowing and willing, you need to leave plenty of good documentation. I haven’t been one to write much of anything, and I’ve already fucked up my shell profiles again because of no documentation, but I can give some general pointers:

What runs where?

Why are things configured in certain ways? (ie “$GameServer gets 4gb because going over creates GC stutters”, “$IP is blocked because of telemetry”, “$File is symlinked to /dev/null to effectively delete/override a rule from $SomewhereElse”)

List rules and their exceptions. (ie “Service ports are numbered this way because it looks nice”, “Except $Port because it conflicts with $SystemService”)

List things even if they’re from personal preference (ie “Service ports are numbered this way because it looks nice”, tells user that these are effectively meaningless and things shouldn’t break by changing these, barring common sense)

Basically, leave meaningful comments that explain why something is the way that it is. You should be able to use this documentation yourself as reference material. Keep this documentation updated regularly, as frequently quoted “bad documentation is worse than no documentation” (or something like that)

(sorry if this last section in particular doesn’t make much sense, I haven’t slept in $hours. feel free to ask for clarification!)
source
- abeorch@lemmy.ml ⁨4⁩ ⁨months⁩ ago
  Yeah I have some friends. Id like to make it easier for them. (With some recognition as well)
  
  source
lemmyvore@feddit.nl ⁨4⁩ ⁨months⁩ ago
Write a document that describes the main points of your setup. That’s about it. You don’t have to teach them everything, just guide them. Like, if you use a certain Linux distro and Docker just say “I use Docker on Debian and the compose files are in that directory”. That should be enough to get someone started if they know Linux and Docker, and if they don’t they’re not going to learn it from your doc, they should go looking for someone who does.

Let’s face it, many of our self-hosted setups are DIY setups we make as a hobby. If you really want an out-of-the-box experience that can be administered by a non-techy there will be limits to what you can achieve.

source
- abeorch@lemmy.ml ⁨4⁩ ⁨months⁩ ago
  Yeah . Im good with writing and try to keep things up to date ( try being the word)
  
  Im also trying to template and standardise - Maybe need to think about a deployment process or something.
  
  source
Lifebandit666@feddit.uk ⁨4⁩ ⁨months⁩ ago
When I die my friends will miss me like usual. Then the Plex server will go down and they’ll miss me all over again.

source
thayer@lemmy.ca ⁨4⁩ ⁨months⁩ ago
My wife and I share a KeePass database for all of our credentials, including the keys to our digital kingdom. I also thoroughly document our LAN design, server setup, and general maintenance notes which, like KeePass, are also shared to her via SyncThing. I also add notes to the KeePass entries, pointing her or my son to the appropriate note file for more info. I will also hints like, “this is the password that decrypts our file server drive…to do this, open a terminal and paste the following…”

She is comfortable pasting commands into a terminal when necessary, so if anything ever happens to me I am confident she will at least be able to access our data, and move it to a more user-friendly or accessible format.

source
- abeorch@lemmy.ml ⁨4⁩ ⁨months⁩ ago
  Is that keepass.info ?
  
  source
  - thayer@lemmy.ca ⁨4⁩ ⁨months⁩ ago
    Yep, that’s the one. We use KeePassDX on mobile and KeePassXC on the desktop.
    
    source
anzo@programming.dev ⁨4⁩ ⁨months⁩ ago
Another consideration would be building communities around platforms and instances. That’s how many of the open source world thrives!

source
- abeorch@lemmy.ml ⁨4⁩ ⁨months⁩ ago
  Yeah this was what I was thinking. Interested in what people have out there. I dont like reinventing the wheel - Id probably make it an irregular polygon
  
  source
  - anzo@programming.dev ⁨4⁩ ⁨months⁩ ago
    There are different approaches or sentiments that bring people together. There’s for example the left-politics platform disroot.org and they have also developed some solutions of their own (as in not only hosting, but coding). Autistici colective has this calendar called ganzo or similar iirc. That’s something amazing to me.
    
    source
    -> View More Comments