INFRAWEAVER ALPHA

infraweaver/support

Support and community

There is no commercial support tier, no enterprise contract and no response-time commitment. What exists is a repository, an issue tracker, and a maintainer who reads them.

Where to go

A BUG

Open an issue on the platform repository. Include the commit you are on, the manifest or route involved, and the output that surprised you.

A SECURITY FINDING

A private security advisory, not a public issue. See security for what to include and what to expect.

A QUESTION

Read the FAQ and docs/TROUBLESHOOTING.md first. Most questions are already answered from a real incident. Then open a discussion.

What makes a report worth answering

This project is maintained in spare time. A report that lets someone reproduce the problem in five minutes gets fixed; one that does not usually does not.

  1. The commit, not "the latest"There is no version number to quote. git rev-parse --short HEAD is the answer.
  2. What you expected and what happenedBoth. "It does not work" describes a feeling, not a defect.
  3. The shortest decisive outputThe one line the failure turns on, plus enough context to place it. Not a thousand lines of pod logs.
  4. Your shapeNode count and sizes, which optional groups are on, DNS provider, whether you are behind a proxy. Most reports turn on one of these.
  5. What you already triedSaves the first two replies of every thread.

Contributing

Contributions are welcome. Open an issue before a large pull request. The platform has opinions about layering and secret handling, and it is better to find out before you have written the code.

Two hard rules worth knowing before your first change. Nothing that resolves to a real credential goes into the repository; a CI gate enforces it and will fail your build. And every deployment-specific value is a ${PLACEHOLDER}, filled from .env at generation time. Hardcoding your own domain is the single most common first-PR mistake.

READ FIRST