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

Selfhosted

59999 readers
693 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

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.

(page 2) 19 comments
sorted by: hot top controversial new old
[–] redxef@feddit.org 2 points 1 year ago (1 children)

The whole deployment is done via ansible, so the ansible source is my documentation.

[–] SidewaysHighways@lemmy.world 1 points 1 year ago

fuck yeahhh man that sounds like the absolute best. I'm really looking forward to the time when i get to learn Ansible

[–] Shimitar@downonthestreet.eu 2 points 1 year ago

Here: https://wiki.gardiol.org/

Based on Dokuwiki and my own experience. Mostly started to track what and why I do stuff, and published because I truly believe in a free internet.

[–] fmstrat@lemmy.nowsci.com 2 points 1 year ago (1 children)

Every time I set up anything, I do one of two things:

  • If it's container based, it gets a commented docker compose file in my custom orchestration

  • If it's on a host system, the changes are scripted and commented in a setup script, which are run on new machines. If the acrit is specific to one machine, it is configured as such

I find in-setup docs to be best for a home lab, plus if I have to replace hardware, it's fast.

Fun fact, I do it for laptops and desktops, too.

[–] CapitalNumbers@lemm.ee 2 points 1 year ago (1 children)

this is basically what i ended up doing to - glad to see my approach verified somewhat ha ha!

but yeah, in general whenever i make a change / add new service, i always try and add those steps to some sort of setup.sh / docker-compose

[–] fmstrat@lemmy.nowsci.com 1 points 1 year ago

Yea comes in super handy when you always want dropbear SSH for remote unlock, or making sure both RAID disks boot, etc.

I do it for all my software setup, too. A shell script for each, then a for loop that asks to run each. But I also made https://github.com/fmstrat/gam, so maybe I just like overkill bash.

[–] tofu@lemmy.nocturnal.garden 2 points 1 year ago

I started to put it all in my selfhosted bookstack and that works well for me. I also automated a good part of my setup with Ansible, so I can just check how the Playbook did things if I forgot.

[–] Oisteink@lemmy.world 1 points 1 week 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

[–] corsicanguppy@lemmy.ca 1 points 1 year ago

In gitlab.

In the terraform project that builds it. Or in the cinc.sh config that makes it go.

MD lets me add diagrams.

[–] TCB13@lemmy.world -5 points 1 year ago (3 children)

If it need documentation means things are over the line when comes to complexity and I should scale down / simplify. :)

Complexity and over-engineering are a serious problem, I really try to keep it as simple as possible so I don't have to waste time managing it, dealing with updates and potential security issues. Simple code/infrastructure breaks less and has less potential insecure points.

load more comments (3 replies)
load more comments
view more: ‹ prev next ›