Selfhosted

38789 readers

373 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:

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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Design patterns (lemmy.ml)

submitted 1 month ago by [email protected] to c/[email protected]

18 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

[–] [email protected] 9 points 1 month ago (1 children)

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.

[–] [email protected] 2 points 1 month 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.