Change tracking ideas (lemmy.procrastinati.org)

submitted 6 months ago by SeeJayEmm@lemmy.procrastinati.org to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[-] spaghetti_carbanana@krabb.org 2 points 6 months ago

Back in the day when the self-hosted $10 license existed I was using JIRA Service Desk to do this. As far as ticketing systems go it was very easy to work with and didn't slow me down too much.

I know you don't want a ticket system but I'm just curious what other people will suggest because I'm in the same boat as you.

Currently I haphazardly use Joplin to take very loose notes and sync them to Nextcloud.

If you want a very simple option with minimal setup and overhead you could use Joplin to create separate notes for each "part" of your lab and just add a new line with a date, time and summary of the change.

I do also use SnipeIT to track all my hardware and parts, which allows you to add notes and service history against the hardware asset.

Other than that, I'm keen to see what everyone else says

[-] SeeJayEmm@lemmy.procrastinati.org 2 points 6 months ago

I know you don’t want a ticket system but I’m just curious what other people will suggest because I’m in the same boat as you.

I'm not opposed to a ticketing system but I'd want something pretty simple. Last one I tried was GLPI because I thought the inventory mgmt + ticketing would be useful but it was just way too much.

Currently I haphazardly use Joplin to take very loose notes and sync them to Nextcloud.

I'm currently using Wiki.js (synced to GitHub) in an attempt to document things. I've played with a changelog section but it's like a stream of consciousness and I'm not real happy with the layout.

I do also use SnipeIT to track all my hardware and parts, which allows you to add notes and service history against the hardware asset.

That looks cool. I may check that out.

Thanks

this post was submitted on 05 Mar 2024

22 points (95.8% liked)

Selfhosted

39251 readers

209 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz