submitted 2 years ago by abeorch@lemmy.ml to c/selfhosted@lemmy.world

19 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[-] lemmyvore@feddit.nl 9 points 2 years 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.ml 2 points 2 years 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.

this post was submitted on 12 Jul 2024

39 points (95.3% liked)

Selfhosted

61901 readers

873 users here now

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:

Detailed Rules Post

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!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world