this post was submitted on 19 Jun 2023
27 points (96.6% liked)

Selfhosted

39933 readers
321 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago (1 children)
[–] KeepFlying 1 points 1 year ago (2 children)

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...)

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] KeepFlying 1 points 1 year ago

This is one of the main reasons I want to move to Ansible or develop my docker skills a bit more. Having a true infra as code that's all versioned would be amazing. Right now I'm about half and half.

[–] sudneo 1 points 1 year ago

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.