Selfhosted

61021 readers

667 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

124

What do you use to document your home lab? (lemmy.procrastinati.org)

submitted 3 years ago* (last edited 3 years ago) by SeeJayEmm@lemmy.procrastinati.org to c/selfhosted@lemmy.world

114 comments fedilink hide all child comments

My home lab has a mild amount of complexity and I'd like practice some good habits about documenting it. Stuff like, what each system does, the OS, any notable software installed and, most importantly, any documentation around configuration or troubleshooting.

i.e. I have an internal SMTP relay that uses a letsencrypt SSL cert that I need to use the DNS challenge to renew. I've got the steps around that sitting in a Google Doc. I've got a couple more google docs like that.

I don't want to get super complicated but I'd like something a bit more structured than a folder full of google docs. I'd also like to pull it in-house.

Thanks

Edit: I appreciate all the feedback I've gotten on this post so far. There have been a lot of tools suggested and some great discussion about methods. This will probably be my weekend now.

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

[–] floofloof@lemmy.ca 14 points 3 years ago* (last edited 3 years ago) (2 children)

Mine is, er, self-documenting, and my partner has instructions, in the event that I die, to plug the wifi router into the modem and unplug all the other crap. The router has a sticker saying ROUTER and the modem has a sticker saying MODEM.

[–] johntash@eviltoast.org 5 points 3 years ago (1 children)

Self documenting, eh? I may be familiar with the same process.

[–] floofloof@lemmy.ca 8 points 3 years ago

You just follow all the wires and read all the config files. Easy!

[–] limit@lemmy.world 2 points 3 years ago (1 children)

As I move to more self hosting, it's becoming more and more important to create a "what to do if I die" procedure for my wife (or even children) to follow. I mean it's not big deal if the plex server goes down and doesn't come back up, I'm thinking more along the lines of all of our photos, important documents, password manager, those type of things. I have 3 - 2 - 1 backups for the important stuff and have tested them, but that means nothing to my wife if I wasn't around to get that stuff back if something happened.. I wonder some days if I should document it all and put a print out with a step by step guide on how to get everything back that a semi tech savvy person could follow.

[–] floofloof@lemmy.ca 2 points 3 years ago* (last edited 3 years ago)

Yes, I really need to do this too. It's a fairly daunting task because my significant other is not at all comfortable with even slightly complicated operations on a computer. I need to figure out a way to make a really easily accessible backup of everything.