Does anyone have any recommendations for issue tracking for homelab setups? I’m sure I could host some Jira clone but that feels overkill for what I’m doing, and something like MediaWiki is too general purpose.
I’m hoping to track future project ideas (Install Jellyfin / Sonarr, etc) and issues with my smarthome (Fireplace Light not accepting color changes via Google Assistant). Ideally with some kind of organization to it (priorities, subitems, etc).
Yeah I could use plaintext, but that’s no fun :)
Nextcloud Deck
Vikunja has become my whole life todo list app and I throw server stuff on there too. I’ve enjoyed it quite a bit.
I use a combination of Obsidian and Notion to track my home lab. Obsidian is all the detailed configs and todo’s, while Notion is the documentation for the rest of the family
I’m trying to move off of Things 3, since I tried to consolidate daily/life tasks with a different section for my lab. Yeah, that hasn’t worked out too well so far. My new job uses GitLab exclusively, so I figure that might be a good pain point to learn the ins/outs of, including issue tracking.
As you said, the easiest method would be to do it in plaintext.
Something like:
- Create a file with an identifier and timestamp for an issue.
- If the solution is in a repository, reference commit link.
- Regardless of whether there is version history with proof of fix, note down the solution in brief underneath the issue.
- On top of the file, mark issue as closed.
One can have a template for this along with an automated shell script or something. Nice project for a couple of hours. I might actually do something like this myself when I get to it. Thanks for the idea
I actually use GitLab for a ton of this stuff plus all my dev work. The issues and boards are all I need, and can be tracked at the group level, so why add another tool?
Emacs org-mode, although with minimal organsation (just a single tag typically, which org-agenda then shows in my calendar if I’ve scheduled it for a certain time). It does support priorities too, but I don’t typically use that.
I don’t, that sounds too much like work. I do what I want when I feel like it.
I have used Trello for idea tracking in the past.
I’ve seen this post a day or two ago and told myself I would try it one day. Maybe it works for your usecase as well.
I landed on Trello for managing my entire life. Personal projects, work projects, home projects, whatever: there’s a board and 200 cards for things I’ll never actually do :P
It’s not self-hosted, but it’s free for a limited number (5?) of boards and I mean, good enough.
This might be the best option honestly, though self hosted would be a bit better of course.
Thank you, I got tunnel vision to selfhosted options.
If you want to self-host, Vikunja is a pretty good replacement for Trello.
As a direct kanban alternative to Trello, Kanboard is a focused & uncluttered selfhosted option.
I use Gitea issues
Does gitea let you have issues that do t belong to a specific project?
My smarthome isn’t backed by a git repo, and having a phantom placeholder project isn’t super appealing to me to force things to work. (though Ill take a look, may be worth the fuss, especially since I could use a gitea instance anyway…)
I actually don’t know, I create issues by repo. I have 2 servers, so 2 repos. Any time I change anything I create an issue in the repo for that server.
I also use gitea, in a bit unstructured way. I do have a dedicated project which I use for project “management” (I.e. dump ideas about new services, new tools to write, improvements and sometimes bugs to fix), I also use repo specific issues for things that concern that particular repo (I have terraform repos, ansible repo, code repos, kubernetes/flux repos etc.). I also use taskwarrior for my actual to do list, which is more general than my homelab.
The main point for me is just not to forget about stuff, but I don’t want to do issue tracking in a way that feels like my second job. For this gitea projects work quite nicely, and they are easily tied to PRs, so that I can go back and easily cross reference what I did for a specific issue.
