Comment on **How** should I properly document my homelab?

• dbtng@eviltoast.org ⁨3⁩ ⁨weeks⁩ ago

  Netbox is a hell of a package, of which I’ve essentially only touched the IPAM, and I don’t even use it programmatically. I just use the web console to keep track of 4 subnets and about 50 IPs.

  It’s got a whole virtualization section that I haven’t touched, although that would make my device mapping more sensible. I just treat em like they are all real, and only map the physical nics on the hypervisor hosts.

  I do keep text notes in Netbox entries, but that’s sort of a backup. If its something I’m likely to need to know, I’ll have a note in Proxmox. Usually login links for apps hosted there and the like. And of course I’ve got a folder full of text files with all my deepest secrets.

  source

  • philpo@feddit.org ⁨3⁩ ⁨weeks⁩ ago

    Netbox,especially when combinded with Plugins is so incredibly good and might,that’s it’s almost funny how good it is. What I do Plugin wise:

    • Documents: not implemented yet by me,but one could store manuals,etc. directly within netbox.

    • Lifecycle and Inventory: While it’s not as good as snipe-it (tbh, inventory is imho one of the worst plugins) it does the job for my small deployment

    • Slurp it to scan automatically

    • QR Code for obvious reasons

    • Floorplan as well

    Of course that sounds overkill for a small deployment, but I simply forget too many things after a few months otherwise and it’s something my family (wife is in IT and far more qualified than me) would need if something happens to me,so a proper documentation would be essential for that as well.

    source

    • dbtng@eviltoast.org ⁨3⁩ ⁨weeks⁩ ago

      Alright already! I’ll work on my upgrade.
      I’m wondering if I should just build a new docker and then migrate the data instead of upgrading in place. I bet that’s the easier thing to do in the end.

      source