Selfhosted

39980 readers

487 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]

What do you all use for issue tracking for your systems? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

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] 1 points 1 year ago

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