Selfhosted

39980 readers

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

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Change tracking ideas (lemmy.procrastinati.org)

submitted 8 months ago by [email protected] to c/[email protected]

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

[–] [email protected] 1 points 8 months ago (1 children)

I do have a couple github repos for various things (ansible, scripts, dns). My plan for general documentation is the wiki. I've started the work on that but it's far from complete (those get saved in markdown and synced to github). Maybe the simplest solution is the one I'm avoiding. Just putting it all in a readme/changelog.

[–] [email protected] 3 points 8 months ago (1 children)

I would encourage you not to split things up too finely. A single repo for your environment would allow you to see all related changes with git. E.g. if you set up a new VM it might need a playbook to set something up, a script to automate a task, and a DNS entry. With a well put together commit message explaining why you're making those changes there's not much need for external documentation.

Maybe if you want some more info organised in a wiki, point to the initial commit where you introduced some set up. That way you can see how something was structured. Or if you have a issue tracker you can comment with research on something and then close the issue when you commit a resolution.

Try not to have info spread out too much or maintaining all the pieces will become a chore. Make it simple and easy to keep up.

[–] [email protected] 1 points 8 months ago

Try not to have info spread out too much or maintaining all the pieces will become a chore. Make it simple and easy to keep up.

I think you're right on this point. I have a tendency to over-complicate things and that leads to them getting scrapped or neglected.