Selfhosted

40198 readers

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

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 1 year ago

MODERATORS

[email protected]

Design patterns (lemmy.ml)

submitted 4 months ago by [email protected] to c/[email protected]

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

[–] [email protected] 18 points 4 months ago* (last edited 4 months ago) (4 children)

Not about design patterns, but about making preparations: https://github.com/potatoqualitee/eol-dr

[–] [email protected] 2 points 4 months ago (2 children)

Useful I have some of this but not other bits. A bit morbid but Im interested in what the break glass mechanism would be.

[–] [email protected] 1 points 4 months ago (1 children)

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. 😅

[–] [email protected] 1 points 4 months ago

Yes definitely. Trust is the key

load more comments (1 replies)