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

Selfhosted

46672 readers
730 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 posting.

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

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 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
[–] [email protected] 3 points 4 days ago

🧠 + a few slapdash notes in a password manager. It's very organic, very human.

Occasionally leads to situations like this.

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

But what about the documentation to host the note server?

load more comments (1 replies)
[–] [email protected] 2 points 4 days ago* (last edited 4 days ago)

I tried since the very beginning to build everything in ansible and terraform, so everything is in the code or in its associated README files.

But apart from that I have a hodge podge of dozens of note documents in Obsidian.

[–] [email protected] 2 points 4 days ago

Obsidian synced via git.

[–] [email protected] 2 points 4 days 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.

[–] [email protected] 2 points 4 days 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.

[–] [email protected] 2 points 4 days ago* (last edited 4 days ago)

Not much, really. I do comment changes to config files and such.

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

NixOS's declarative configurations basically document themsleves: add some comments and you're good to go and can back then up to wherever whenever

[–] neidu3 1 points 4 days ago

I typically don't. Most of my setup is based on habits formed over decades, so not a whole lot is needed for me to figure out stuff. If I do something that is atypical of me I usually add it to /etc/motd as a reminder.

[–] [email protected] -5 points 4 days 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 β€Ί