AlreadyOn

REAL HOMELABS. USEFUL FEEDBACK.

Something off?
Let’s figure it out.

You don’t need to be a developer to help. Tell us what you tried, what you expected, and what happened instead.

SOMETHING ISN’T WORKING

Report a bug
or ask for help.

A clear example is more useful than a technical diagnosis. If you aren’t sure what caused the problem, say so.

Open a bug report ↗
YOU HAVE AN IDEA

Recommend
a change.

Describe the part of watching or managing your library that could be better, and how you’d like it to feel.

Suggest an improvement ↗

Your first GitHub issue.

  1. Check whether someone already reported it.

    Search existing issues for a few words describing the problem. Add helpful details to an existing issue if it matches.

  2. Sign in to GitHub.

    You’ll need a GitHub account to submit or comment. If you don’t have one, create an account, then return to the bug or feature link above.

  3. Give the issue a specific title.

    “Google TV guide opens, but selecting a channel shows a black screen” gives us more to work with than “Broken.” Fill in the form as best you can.

  4. Show us the steps.

    Include what happened, what you expected, steps to reproduce, your AlreadyOn version or image tag, device/browser and OS, and whether this is Docker or a NAS installation. A sanitized screenshot or small log excerpt can help.

  5. Watch for a follow-up.

    We may ask for another detail or a test on a newer release. Updates in the same issue keep the conversation together. This is a community project; responses may take time.

For feature ideas: explain the problem first, your proposed change, and what a successful result would look like. A concrete example from your household is especially helpful.

BEFORE YOU PRESS SUBMIT

Keep private things private.

GitHub issues are public. Remove passwords, pairing PINs, API keys, tokens, private addresses, personal file paths, and identifying details from screenshots and logs. Don’t upload your database or configuration folder.

If you think you found a security vulnerability, use the project’s private security reporting route rather than posting exploit details publicly. See the security policy for the fallback if private reporting is unavailable.

AlreadyOn’s public repository is the place for tester feedback. Internal development planning happens separately, so you don’t need to navigate our development tracker.