I’d like to start doing a better job of tracking the changes I made to my homelab environment. Hardware, software, network, etc. I’m just not sure what path I want to take and was hoping to get some recommendations. So far the thoughts I have are:

  • A change history sub-section of my wiki. (I’m not a fan of this idea.)
  • A ticketing system of some sort. (I tried this one and it was too heavy. I’d need to find a simple solution.)
  • A nextcloud task list.
  • Self-host a gitlab instance, make a project for changes and track with issues. Move what stuff I have in github to this instance and kill my github projects. (It’s all private stuff.)

I know that several of you are going to say “config as code” and I get it. But I’m not there yet and I want to track the changes I’m making today.

Thanks

  • thayer@lemmy.caEnglish
    3·
    9 months ago

    I try to keep things simple and just use Markdown files for everything. I have a doc for each physical device, and another doc for each service/container running on the LAN.

    I generally track hardware specs, upgrade paths, and software changelogs/todos as unsorted lists within these docs. It’s super portable and easily synced across devices via Syncthing.