Add NGINX Ecosystem

[dvershinin]

https://github.com/GetPageSpeed/awesome-nginx#readme

NGINX is the web server, reverse proxy, and load balancer behind a large share of the web. This list covers its production ecosystem: third-party modules, distributions and forks (Angie, freenginx, OpenResty, Tengine), security/WAF tooling, packaging, and learning resources — about 200 entries, every one verified in production use.

Note on the existing nginx entry in this category: that list is a general collection of articles and resources. This one is complementary, focused on the module and packaging ecosystem: which modules exist, which are maintained, and how to deploy them. Renamed the entry to NGINX Ecosystem following a reviewer suggestion to make that distinction unambiguous at a glance.

The list is over 30 days old (first commit 2026-06-02), passes awesome-lint in CI on every push, is CC0-licensed, and has contribution guidelines.

Reviewed PRs (4) — see follow-up comment.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

• Fully AI-generated pull requests are not accepted.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 4 other open pull requests. (see follow-up comment for links)
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
• Your entry should be added at the bottom of the appropriate category.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
• No blockchain-related lists.

Requirements for your Awesome list

• Has been around for at least 30 days. First commit: 2026-06-02.
• Is not AI-generated.
• Run awesome-lint on your list and fix the reported issues. Passing in CI on every push.
• The default branch should be named main.
• Includes a succinct description of the project/theme at the top of the readme.
• It's the result of hard work and the best I could possibly produce. 200+ entries, every one verified in production use, curated over years of NGINX packaging work.
• The repo name of your list should be in lowercase slug format: awesome-nginx.
• The heading title of your list should be in title case format: # Awesome NGINX.
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics.
• Not a duplicate. The existing nginx-resources list is a different scope (articles/resources); this one — titled NGINX Ecosystem — covers the module/packaging ecosystem.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. CI link auditing ensures this on every push.
• Includes a project logo/illustration.
• Entries have a description.
• Includes the Awesome badge.
• Has a Table of Contents section named Contents.
• Has an appropriate license. CC0.
• Has contribution guidelines (contributing.md).
• Has consistent formatting and proper spelling/grammar.
• Does not use hard-wrapping.
• Does not include a CI badge.
• Does not include an "Inspired by awesome-foo" link.

[dvershinin]

unicorn

[dvershinin]

Reviewed PRs:

• Add awesome-python-bots, awesome-python-scrapers, awesome-crypto-python #4313
• Add Agentic Engineering #4286
• Add SRE Agents #4262
• Add Testing Tools #4265

[yudataguy]

Nicely done — awesome-lint passes cleanly and the list is thorough. Two things to check:

• License: GitHub reports the repo license as NOASSERTION (it can't identify it). The guidelines require a recognized Creative Commons license (CC0 recommended) — worth confirming yours is detected correctly.
• Duplicate category: there's already an nginx entry (fcambus/nginx-resources) in this section. You address this in the description, and the focus does differ (production ecosystem vs. articles) — just flagging it since "not a duplicate" is an explicit requirement the maintainer will weigh.
• Minor: consider an Oxford comma — "Web server, reverse proxy, and load balancer."

[dvershinin]

Thanks for the thorough review, @yudataguy. All three items addressed:

• License: The repo was using the verbose "Creative Commons Legal Code" form of CC0, which GitHub's licensee doesn't fingerprint. Replaced with the canonical SPDX short form — GitHub now shows CC0-1.0. Commit: GetPageSpeed/awesome-nginx@9317922
• Oxford comma: Fixed in both the entry line and the PR description — "Web server, reverse proxy, and load balancer."
• Duplicate note: Acknowledged; the complementary-scope framing stays in the description for the maintainer to weigh.

[anupddas]

Thanks @dvershinin

[cYoren]

Great list of production-grade modules and tools! The layout is extremely clean and compliant. One suggestion: the list uses emojis like 📦 and ⭐ to highlight packages and author-owned repositories. While informative, awesome lists generally prefer to minimize self-promotion symbols to maintain an objective tone. It could be worth clarifying or toning down these markers in the intro, but the content quality itself is excellent.

[Mo-way]

@dvershinin For the checklist lgtm.

For the name, I suggest using a different name than existing list to avoid confusion, e.g. nginx modules.

[dvershinin]

Thanks both, addressed:

• @cYoren — dropped the ⭐ (self-authored) marker entirely, that's the real self-promotion signal. Kept 📦 but reframed it as an objective "available as an RPM/DEB package" install marker, and reworded the intro out of first person too. GetPageSpeed/awesome-nginx@a4d5c33
• @Mo-way — renamed the entry to NGINX Ecosystem to make it unambiguous next to the existing nginx entry. Also squashed the PR to a single commit per the guidelines.

[Mo-way]

@dvershinin Great! But list in repo ist still old name. Intended? Personally, I'd align it

[Egv2]

solid list, well organized. one concern:

1. there is a <!-- BEGIN GENERATED --> comment at the top which suggests this list is auto-generated from a YAML pipeline. awesome lists are typically manually curated. might be worth removing that comment and the indication that it is machine-generated.

2. a lot of entries link to repos owned by GetPageSpeed or dvershinin (the PR author). while these might be legitimate projects, having so many self-referential links could be seen as self-promotion. might want to diversify the entry sources or add a note about the relationship.

the packaging and module coverage is really thorough though :)

[dvershinin]

Yes, intentional. “NGINX Ecosystem” is the label used here to distinguish it from the existing nginx entry, while the repository keeps the conventional “Awesome NGINX” project title.

[dvershinin]

Thanks. I’ll keep the current format unless the maintainer requests a change. Every entry is individually curated against the same relevance, maintenance, documentation, and production-use criteria regardless of ownership. I also removed the author-owned marker and kept the presentation neutral, while retaining technically relevant projects that meet the same bar.

[Leon-SG]

Review notes (guideline checklist)

1. Placement: Entries must be added at the bottom of the category. This inserts NGINX Ecosystem mid-way through the hosting/infra-related block rather than at the end of that section.
2. Possible overlap: There is already an nginx-related list in Awesome (general nginx resources). The PR body explains complementarity well — consider making the one-line description stress the module/packaging ecosystem angle so it is not read as a duplicate of general nginx resource lists (e.g. “Third-party modules, forks, and packaging for NGINX.”).
3. Title + URL: Title casing and #readme URL look correct. Description ends with a period — good.

Minor polish on placement + differentiation would strengthen the submission.