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/packaging ecosystem (which modules exist, which are maintained, how to deploy them), curated via a YAML pipeline with CI link auditing on every change, so dead or abandoned entries cannot survive a regeneration. Renamed the entry to NGINX Ecosystem (from 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)
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.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/4316
**Author:** [@dvershinin](https://github.com/dvershinin)
**Created:** 7/5/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `main`
---
### 📝 Commits (1)
- [`a50d889`](https://github.com/sindresorhus/awesome/commit/a50d889ab1319f46c63a7960ea77f1f6107fcdb0) Add NGINX Ecosystem
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -0)
</details>
### 📄 Description
**https://github.com/GetPageSpeed/awesome-nginx#readme**
[NGINX](https://nginx.org/) 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](https://github.com/fcambus/nginx-resources#readme) entry in this category: that list is a general collection of articles and resources. This one is complementary, focused on the module/packaging ecosystem (which modules exist, which are maintained, how to deploy them), curated via a YAML pipeline with CI link auditing on every change, so dead or abandoned entries cannot survive a regeneration. Renamed the entry to **NGINX Ecosystem** (from 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.
- [x] 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.
- [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive.
- [x] **You have to review at least 4 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** (see follow-up comment for links)
- [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md).
- [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`.
- [x] 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.
- [x] Your entry should be added at the bottom of the appropriate category.
- [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`.
- [x] No blockchain-related lists.
## Requirements for your Awesome list
- [x] **Has been around for at least 30 days.** First commit: 2026-06-02.
- [x] Is not AI-generated.
- [x] Run `awesome-lint` on your list and fix the reported issues. Passing in CI on every push.
- [x] The default branch should be named `main`.
- [x] **Includes a succinct description of the project/theme at the top of the readme.**
- [x] 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.
- [x] The repo name of your list should be in lowercase slug format: `awesome-nginx`.
- [x] The heading title of your list should be in title case format: `# Awesome NGINX`.
- [x] Non-generated Markdown file in a GitHub repo.
- [x] The repo should have `awesome-list` & `awesome` as GitHub topics.
- [x] Not a duplicate. The existing `nginx-resources` list is a different scope (articles/resources); this one — titled **NGINX Ecosystem** — covers the module/packaging ecosystem.
- [x] Only has awesome items. Awesome lists are curations of the best, not everything.
- [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. CI link auditing ensures this on every push.
- [x] Includes a project logo/illustration.
- [x] Entries have a description.
- [x] Includes the Awesome badge.
- [x] Has a Table of Contents section named `Contents`.
- [x] Has an appropriate license. CC0.
- [x] Has contribution guidelines (`contributing.md`).
- [x] Has consistent formatting and proper spelling/grammar.
- [x] Does not use hard-wrapping.
- [x] Does not include a CI badge.
- [x] Does not include an "Inspired by awesome-foo" link.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/4316
Author: @dvershinin
Created: 7/5/2026
Status: 🔄 Open
Base:
main← Head:main📝 Commits (1)
a50d889Add NGINX Ecosystem📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
readme.md(+1 -0)📄 Description
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/packaging ecosystem (which modules exist, which are maintained, how to deploy them), curated via a YAML pipeline with CI link auditing on every change, so dead or abandoned entries cannot survive a regeneration. Renamed the entry to NGINX Ecosystem (from 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
Add Name of List. It should not contain the wordAwesome.#readme.Requirements for your Awesome list
awesome-linton your list and fix the reported issues. Passing in CI on every push.main.awesome-nginx.# Awesome NGINX.awesome-list&awesomeas GitHub topics.nginx-resourceslist is a different scope (articles/resources); this one — titled NGINX Ecosystem — covers the module/packaging ecosystem.Contents.contributing.md).🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.