Mod ref manual import for preview

Author: TasoOneAsia

config/_default/config.toml

@@ -1,7 +1,7 @@
 baseURL = "/"
 languageCode = "en-us"
 title = "NGINX Documentation"
-refLinksErrorLevel = "ERROR"
+refLinksErrorLevel = "warning"
 pygmentsCodeFences = true
 pygmentsUseClasses = true
 enableGitInfo = true

content/nginx/directives.md

@@ -0,0 +1,64 @@
+---
+title: Connection processing methods
+description: Connection processing methods
+toc: true
+nd-org-source: events.xml
+---
+
+
+<!--
+      ********************************************************************************
+      🛑 WARNING: AUTOGENERATED FILE - DO NOT EDIT 🛑 This Markdown file was
+      automatically generated from the source XML documentation. Any manual
+      changes made directly to this file will be overwritten. To request or
+      suggest changes, please edit the source XML files instead.
+      https://github.com/nginx/nginx.org/tree/main/xml/en
+      ********************************************************************************
+      -->
+
+
+nginx supports a variety of connection processing methods.
+The availability of a particular method depends on the platform used.
+On platforms that support several methods nginx will normally
+select the most efficient method automatically.
+However, if needed, a connection processing method can be selected
+explicitly with the
+[use]({{< relref "ngx_core_module#use" >}}) directive.
+
+The following connection processing methods are supported:
+
+- `select` — standard method.
+The supporting module is built automatically on platforms that lack
+more efficient methods.
+The `--with-select_module` and
+`--without-select_module` configuration parameters
+can be used to forcibly enable or disable the build of this module.
+
+- `poll` — standard method.
+The supporting module is built automatically on platforms that lack
+more efficient methods.
+The `--with-poll_module` and
+`--without-poll_module` configuration parameters
+can be used to forcibly enable or disable the build of this module.
+
+- `kqueue` — efficient method used on
+FreeBSD 4.1+, OpenBSD 2.9+, NetBSD 2.0, and macOS.
+
+- `epoll` — efficient method used on
+Linux 2.6+.
+
+> The `EPOLLRDHUP` (Linux 2.6.17, glibc 2.8) and `EPOLLEXCLUSIVE` (Linux 4.5, glibc 2.24) flags are supported since 1.11.3.
+
+
+> Some older distributions like SuSE 8.2 provide patches that add epoll support to 2.4 kernels.
+
+
+- `/dev/poll` — efficient method used on
+Solaris 7 11/99+, HP/UX 11.22+ (eventport), IRIX 6.5.15+,
+and Tru64 UNIX 5.1A+.
+
+- `eventport` — event ports, method
+used on Solaris 10+ (due to known issues,
+it is recommended using the `/dev/poll` method instead).
+
+

content/nginx/module-reference/events.md

@@ -0,0 +1,100 @@
+---
+title: ngx_http_access_module
+description: ngx_http_access_module
+toc: true
+nd-org-source: http/ngx_http_access_module.xml
+nd-commercial: false
+nd-commercial-partial: false
+---
+
+
+<!--
+      ********************************************************************************
+      🛑 WARNING: AUTOGENERATED FILE - DO NOT EDIT 🛑 This Markdown file was
+      automatically generated from the source XML documentation. Any manual
+      changes made directly to this file will be overwritten. To request or
+      suggest changes, please edit the source XML files instead.
+      https://github.com/nginx/nginx.org/tree/main/xml/en
+      ********************************************************************************
+      -->
+
+
+The `ngx_http_access_module` module allows
+limiting access to certain client addresses.
+
+Access can also be limited by
+[password]({{< relref "ngx_http_auth_basic_module" >}}), by the
+[result of subrequest]({{< relref "ngx_http_auth_request_module" >}}),
+or by [JWT]({{< relref "ngx_http_auth_jwt_module" >}}).
+Simultaneous limitation of access by address and by password is controlled
+by the [satisfy]({{< relref "ngx_http_core_module#satisfy" >}}) directive.
+## Example Configuration
+
+
+```nginx 
+location / {
+    deny  192.168.1.1;
+    allow 192.168.1.0/24;
+    allow 10.1.1.0/16;
+    allow 2001:0db8::/32;
+    deny  all;
+}
+ ```
+
+
+The rules are checked in sequence until the first match is found.
+In this example, access is allowed only for IPv4 networks
+`10.1.1.0/16` and `192.168.1.0/24`
+excluding the address `192.168.1.1`,
+and for IPv6 network `2001:0db8::/32`.
+In case of a lot of rules, the use of the
+[ngx_http_geo_module]({{< relref "ngx_http_geo_module" >}})
+module variables is preferable.
+## Directives
+
+### allow
+
+{{< ngx-directive >}}
+
+<tr>
+<th>Syntax: </th>
+<td><code><strong>allow</strong> <i>address</i> <i>|</i> <i>CIDR</i> <i>|</i> <i>unix:</i> <i>|</i> <i>all</i>;</code><br/></td>
+</tr><tr>
+<th>Default: </th>
+<td>
+      —
+    </td>
+</tr><tr>
+<th>Context: </th>
+<td><code>http</code>, <code>server</code>, <code>location</code>, <code>limit_except</code></td>
+</tr>
+
+{{< /ngx-directive >}}
+
+
+Allows access for the specified network or address.
+If the special value `unix:` is specified (1.5.1),
+allows access for all UNIX-domain sockets.
+### deny
+
+{{< ngx-directive >}}
+
+<tr>
+<th>Syntax: </th>
+<td><code><strong>deny</strong> <i>address</i> <i>|</i> <i>CIDR</i> <i>|</i> <i>unix:</i> <i>|</i> <i>all</i>;</code><br/></td>
+</tr><tr>
+<th>Default: </th>
+<td>
+      —
+    </td>
+</tr><tr>
+<th>Context: </th>
+<td><code>http</code>, <code>server</code>, <code>location</code>, <code>limit_except</code></td>
+</tr>
+
+{{< /ngx-directive >}}
+
+
+Denies access for the specified network or address.
+If the special value `unix:` is specified (1.5.1),
+denies access for all UNIX-domain sockets.