Selfhosted

39159 readers

380 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]

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

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

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

(page 2) 16 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 year ago

I use the wonderful https://draw.io to sketch up my homelab and which device hosting what service. More fun when it's vidualized the way I want it 😊

[–] [email protected] 0 points 1 year ago (1 children)

I use a combination of netbox for the physical/logical network and server connectivity, and outline for text documentation of the different components.

load more comments (1 replies)

[–] [email protected] 0 points 1 year ago (1 children)

Why not push it up to GitHub? Then you also get a commit history to see your changes overtime.

[–] [email protected] 1 points 1 year ago (2 children)

Wow that sounds convinient, where can i find a guide describing this? Has zero experience with git 😅

[–] [email protected] 1 points 1 year ago

There are tons of tutorials around, but the basic gist is that you only use a couple of commands (or even a good frontend) in git, especially when it's a one (wo)man show.

I highly recommend it!

load more comments (1 replies)

[–] [email protected] 0 points 1 year ago (1 children)

What is it that you all are documenting? I'm just getting started and have so far just set up docker and several containers (Plex, the *arrs, qbittorrent, gluetun) and not sure if I should be writing something down?

load more comments (1 replies)

[–] [email protected] -1 points 1 year ago

Capacities

load more comments