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?

  • lemmyvore@feddit.nl
    link
    fedilink
    English
    arrow-up
    9
    ·
    6 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.

    • abeorch@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 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.