HarborFM

Reporting Issues

Found a bug or have an idea for HarborFM? Open a GitHub issue so it can be tracked and fixed.

Before You Open an Issue

  1. Search existing issues to see if the bug or request is already reported.
  2. Check the FAQ and Usage guides for common setup questions.
  3. If you are unsure whether something is expected behavior, say so in the issue.

Bug Reports

When reporting a bug, include as much of the following as you can:

  • What you expected vs what happened
  • Steps to reproduce (numbered, minimal)
  • HarborFM version or image tag (for example ghcr.io/loganrickert/harborfm:latest digest or git commit)
  • How you run it (Docker, Compose/install.sh, Terraform, or local pnpm)
  • Relevant logs (server console, docker logs, or browser console for UI bugs)
  • Browser and OS for web UI issues

Do not paste secrets (JWT_SECRET, API keys, Stripe keys, passwords) into issues.

Feature Requests

Describe the problem you are trying to solve, who it helps, and any alternatives you considered. A short example workflow is more useful than a large wish list.

Open an Issue

Create a new issue here:

https://github.com/LoganRickert/harborfm/issues/new

Related