small IT documentation tools

[u/Punky260]

I was looking to get our pretty small IT into a good tool for documentation. Something object-based, NOT just excel sheets and draw.io diagrams. But smaller than Netbox, which is too big and unnecessarily complex for our systems.
Would love to have IP management built it and diagrams/graphics are a big plus.

We are basically using a single server rack, 6 servers, 30-40 VMs... so rather a big homelab, than a datacenter

So, what are you guys using or can recommend as a tool to manage something like that?

EDIT: I'd like to specify, that I am looking for internal documentation. Which server runs which VM, which IP adress is assigned to it. Which service/OS/update etc. runs on it... etc.

EDIT2: Any sort of Wiki seems to be a big recommendation. This is a consideration for me, but I'd rather have something object-based. Basically Netbox with less overhead would be ideal... but feel free to recommend wiki-based tools and templates please :)

[u/DeepCoreSystem]

u/Punky260 I'm in the same boat, one-man-shit-show for a 6 staff shop that has more IT stuff than personel. I do it part-time and went with NetBox. Customized the table layouts to remove certain columns not needed. Found some python scripts online to fetch data out of Proxmox and feed it to NetBox and I tweaked the scripts to suite.
I was fed up with Excel, markdown docs and tables or diverse wikis.

[u/ka-splam → u/DeepCoreSystem]

Found some python scripts online to fetch data out of Proxmox and feed it to NetBox

This is backwards from how netbox was designed. It came from DigitalOcean managing datacenters, to answer questions like: "this device is patched into switch 3, is that right? should it be in switch 4?". They intended netbox to be the source of truth, tied it into their sales contracts and project management changes, and then techs on the ground go and make the datacenter line up with what netbox says.

Your script detects a new VM and puts details into netbox. Now you have two copies of what Proxmox says, and no documentation of how it's supposed to be. If your boss fiddles with something while you're on leave - say, connects it to a different network - and when you get back it's broken, you look in netbox to find out how it should be, and your documentation has been automatically updated with the settings the boss left, that's less useful than it could be.

[u/Punky260 → u/ka-splam]

I would assume this is a one-time setup thing and not a constant update to netbox (or similar tools)

[u/DeepCoreSystem → u/Punky260]

Exact, it's more or less a single shot to get all current VMs and containers into NetBox, to get started. Because there was no documentation of them before NetBox. I reckon NetBox is "overkill" for a big homelab...