Support

Where to take a question, a problem, or an idea. Four destinations, and you are not expected to pick the right one — see the last section.

A question

Discord — setup help, is this normal?, sharing a configuration, anything conversational. It is the fastest way to reach a person.

Something is broken

Open an issue on the repository it seems to come from. Say what you expected, what happened instead, and which version you are on.

If a running stack is involved, attach a support bundle: lemonfiber support writes one locally, redacts credentials on the way, and sends it nowhere by itself. Read it before you attach it.

An idea, or “it should also do X”

Open it against the spec. A feature request is a proposed change to what the product should do, and this project settles that before code gets written — so the request starts in the specification rather than in an implementation repository.

You do not need to write it as a requirement. Describe the problem and the behaviour you would want; a maintainer shapes it from there.

A security vulnerability

Not through a public issue. Use the private disclosure path in SECURITY.md.

If you cannot tell which of these it is

File it anywhere. Routing is a maintainer’s job, not a reporter’s, and a misrouted report is far better than one nobody makes. Issues are transferred rather than closed and refiled, so nothing is lost by guessing wrong.

What this project does not offer

Paid support, an SLA, or a promised response time. It is maintained in the open, by people who answer because they want to.