this post was submitted on 18 May 2025
3 points (100.0% liked)

Selfhosted

62088 readers
215 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

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

  8. 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:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hello, how do you document your home lab? Whether it's a small server or a big one with firewall and more nodes. I have a small pc with Proxmox and there I have a VM with OpnSense. After I've entered my VPN as a interface in OpenSense, I noticed that I slowly lose the overview with the different rules that I have built in my firewall. And I know that my setup is relatively easy in comparison to others here in this community. I want to have a quick Overview at the various VMs, like the Lxc container, Docker containers that I have in this and the IP addresses that I have assigned to them. I search for a simple an intuitiv way for beginners.

top 7 comments
sorted by: hot top controversial new old
[–] justcallmelarry@lemmy.dbzer0.com 1 points 1 year ago (2 children)

Jokes aside, I do keep some harder to remember stuff written down in a README.md in my repo, but mainly most things are undocumented

[–] nfreak@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

My wife was mentioning the other day that if something happened to me she'd have absolutely no idea how to work any of this shit and that convinced me to actually start documenting it LMAO

Good time to start doing it too. Aside from setting up a NAS this weekend and figuring out an audiobook solution (not something I've ever dabbled with but I really should start reading some communist theory), I've got this project right where I want it for a long while.

[–] jagermo@feddit.org 1 points 1 year ago

"Shit, i hope i remeber the key words i searched for"

[–] nagaram@startrek.website 1 points 1 year ago

I download the YouTube tutorials I followed, upload them to my UAT Jellyfin server, and then when my server is having issues I can't get to the videos!

A flawless system really

I don't, and I know that I'm fucked one day.

[–] Oisteink@lemmy.world 1 points 3 months ago

Now firs of all sorry for necroposting, but i found this while searching. I use claude amd markdown/yaml and serena mcp. We use tmux and shard browser to gather facts. As a bonus i can explain my setup and choices and it will format out nicely

[–] dabe@lemmy.zip 1 points 1 year ago

95% of my homelab lives on a single server, and everything I do is within containers. So, my documentation is just keeping all my compose files in a git repo and writing in comments when necessary. It’s fairly self-documenting, and I haven’t found the need to break out of just using containers for everything, besides a couple things like setting up mergerfs or cockpit, but that’s all plug and play nowadays with stuff like https://projectucore.io/

Of course, I don’t have any other things set up in my physical layout or network stack… but all that stuff would probably just go into an entry in my notes (obsidian/wiki.vim).