Get in touch

No ticket portal, no “your request is important to us” hold music. Two channels, both watched by an actual human: GitHub for anything worth keeping on the record, Discord for the back-and-forth. Pick whichever fits the conversation.

Keep the build server caffeinated

Everything here (the packages, the Docker images, the daily rebuilds) runs on a homelab paid for out of pocket. If the repo saved you an afternoon of compiling nginx by hand, a coffee back the other way is hugely appreciated. No pressure, no paywall, the packages stay free either way.

Buy a coffee via PayPal →

GitHub

Found a bug in a package? Want a module, a patch, or a build flag? Open an issue or a pull request. This is the place for anything that should be public, searchable, and tied to a commit, so the next person who hits the same wall finds your answer waiting.

  • Package build failures and regressions
  • Module requests
  • Security reports (use a private advisory if it’s sensitive)
  • Documentation fixes
Open an issue on GitHub →

Discord

Rather just talk it through? Join the Discord. It’s the place for anything that needs back-and-forth: “is this expected?” questions, getting a build to actually start, or sharing the nginx config that’s almost right.

  • Real-time install and upgrade help
  • Config and tuning chat (nginx, Angie)
  • Early heads-up on new modules
  • Community chat with other repo users
Join the Discord →

Not sure which? If other people will hit it too (a broken package, a missing module, a typo in the docs), use GitHub: it gets indexed and the fix links to a commit. If it’s a “how do I…” or “is this normal?”, Discord is faster and lower-friction. When in doubt, GitHub. Future-you searching at 3 a.m. will thank present-you.