NGINX Management Suite Dimensions Catalog
Information about all of the Dimensions collected by NGINX Agent
{{ range .Site.Data.nms.catalogs.dimensions }} -
-
{{< fa "brands fa-centos" >}} Install NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux
+Install NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux
### Install NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux @@ -39,7 +39,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-ubuntu" >}} Install NGINX Agent on Ubuntu
+Install NGINX Agent on Ubuntu
### Install NGINX Agent on Ubuntu @@ -48,7 +48,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-debian" >}} Install NGINX Agent on Debian
+Install NGINX Agent on Debian
### Install NGINX Agent on Debian @@ -57,7 +57,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-suse" >}} Install NGINX Agent on SLES
+Install NGINX Agent on SLES
### Install NGINX Agent on SLES @@ -66,7 +66,7 @@ NGINX Agent from the repository.
-
{{< fa "solid fa-mountain-sun" >}} Install NGINX Agent on Alpine Linux
+Install NGINX Agent on Alpine Linux
### Install NGINX Agent on Alpine Linux @@ -75,7 +75,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-aws" >}} Install NGINX Agent on Amazon Linux
+Install NGINX Agent on Amazon Linux
### Install NGINX Agent on Amazon Linux @@ -83,7 +83,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-freebsd" >}} Install NGINX Agent on FreeBSD
+Install NGINX Agent on FreeBSD
### Install NGINX Agent on FreeBSD diff --git a/content/nginx-one/agent/install-upgrade/install-from-plus-repo.md b/content/nginx-one/agent/install-upgrade/install-from-plus-repo.md index eb20efab1..85acd8e9d 100644 --- a/content/nginx-one/agent/install-upgrade/install-from-plus-repo.md +++ b/content/nginx-one/agent/install-upgrade/install-from-plus-repo.md @@ -31,7 +31,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-centos" >}} Install NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux
+Install NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux
### Install NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux @@ -40,7 +40,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-ubuntu" >}} Install NGINX Agent on Ubuntu
+Install NGINX Agent on Ubuntu
### Install NGINX Agent on Ubuntu @@ -49,7 +49,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-debian" >}} Install NGINX Agent on Debian
+Install NGINX Agent on Debian
### Install NGINX Agent on Debian @@ -58,7 +58,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-suse" >}} Install NGINX Agent on SLES
+Install NGINX Agent on SLES
### Install NGINX Agent on SLES @@ -67,7 +67,7 @@ NGINX Agent from the repository.
-
{{< fa "solid fa-mountain-sun" >}} Install NGINX Agent on Alpine Linux
+Install NGINX Agent on Alpine Linux
### Install NGINX Agent on Alpine Linux @@ -75,7 +75,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-aws" >}} Install NGINX Agent on Amazon Linux
+Install NGINX Agent on Amazon Linux
### Install NGINX Agent on Amazon Linux @@ -84,7 +84,7 @@ NGINX Agent from the repository.
-
{{< fa "brands fa-freebsd" >}} Install NGINX Agent on FreeBSD
+Install NGINX Agent on FreeBSD
### Install NGINX Agent on FreeBSD diff --git a/content/nginx-one/agent/install-upgrade/uninstall.md b/content/nginx-one/agent/install-upgrade/uninstall.md index 3a7c95aef..6f16d9791 100644 --- a/content/nginx-one/agent/install-upgrade/uninstall.md +++ b/content/nginx-one/agent/install-upgrade/uninstall.md @@ -19,7 +19,7 @@ The user following performing the uninstall steps needs to have `root` privilege Complete the following steps on each host where you've installed NGINX Agent
-
{{< fa "brands fa-centos" >}} Uninstall NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux
+Uninstall NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux
### Uninstall NGINX Agent on RHEL, CentOS, Rocky Linux, AlmaLinux, and Oracle Linux @@ -28,7 +28,7 @@ Complete the following steps on each host where you've installed NGINX Agent
-
{{< fa "brands fa-ubuntu" >}} Uninstall NGINX Agent on Ubuntu
+Uninstall NGINX Agent on Ubuntu
### Uninstall NGINX Agent on Ubuntu @@ -37,7 +37,7 @@ Complete the following steps on each host where you've installed NGINX Agent
-
{{< fa "brands fa-debian" >}} Uninstall NGINX Agent on Debian
+Uninstall NGINX Agent on Debian
### Uninstall NGINX Agent on Debian @@ -46,7 +46,7 @@ Complete the following steps on each host where you've installed NGINX Agent
-
{{< fa "brands fa-suse" >}} Uninstall NGINX Agent on SLES
+Uninstall NGINX Agent on SLES
### Uninstall NGINX Agent on SLES @@ -55,7 +55,7 @@ Complete the following steps on each host where you've installed NGINX Agent
-
{{< fa "solid fa-mountain-sun" >}} Uninstall NGINX Agent on Alpine Linux
+Uninstall NGINX Agent on Alpine Linux
### Uninstall NGINX Agent on Alpine Linux @@ -64,7 +64,7 @@ Complete the following steps on each host where you've installed NGINX Agent
-
{{< fa "brands fa-aws" >}} Uninstall NGINX Agent on Amazon Linux
+Uninstall NGINX Agent on Amazon Linux
### Uninstall NGINX Agent on Amazon Linux @@ -73,7 +73,7 @@ Complete the following steps on each host where you've installed NGINX Agent
-}}OpenAPI v2](/nginx/admin-guide/yaml/v9/nginx_api.yaml) for API version 9 | NGINX Plus Releases [33]({{< ref "/nginx/releases.md#r33" >}}), [34]({{< ref "nginx/releases.md#r34" >}})| The [`/license`](https://nginx.org/en/docs/http/ngx_http_api_module.html#license) data were added|
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v9/nginx_api.yaml) for API version 9 | NGINX Plus Releases [30]({{< ref "nginx/releases.md#r30" >}}), [31]({{< ref "nginx/releases.md#r31" >}}), [32]({{< ref "nginx/releases.md#r32" >}}) | The [`/workers/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#workers_) data were added|
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v8/nginx_api.yaml) for API version 8 | NGINX Plus Releases [27]({{< ref "nginx/releases.md#r27" >}}), [28]({{< ref "nginx/releases.md#r28" >}}), [29]({{< ref "nginx/releases.md#r29" >}}) | SSL statistics for each HTTP [upstream](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_upstream) and stream [upstream](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_stream_upstream), SSL statistics for each HTTP [server zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_server_zone) and stream [server zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_stream_server_zone), extended statistics for [SSL](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_ssl_object) endpoint|
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v7/nginx_api.yaml) for API version 7 | NGINX Plus Releases [25]({{< ref "nginx/releases.md#r25" >}}), [26]({{< ref "nginx/releases.md#r26" >}}),| The `codes` data in `responses` for each HTTP [upstream](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_upstream), [server zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_server_zone), and [location zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_location_zone) were added|
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v6/nginx_api.yaml) for API version 6 | NGINX Plus Releases [20]({{< ref "nginx/releases.md#r20" >}}), [21]({{< ref "nginx/releases.md#r21" >}}), [22]({{< ref "nginx/releases.md#r22" >}}), [23]({{< ref "nginx/releases.md#r23" >}}), [24]({{< ref "nginx/releases.md#r24" >}}) | The [`/stream/limit_conns/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#stream_limit_conns_), [`/http/limit_conns/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#http_limit_conns_), and [`/http/limit_reqs/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#http_limit_reqs_) data were added |
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v5/nginx_api.yaml) for API version 5 | NGINX Plus Release [19]({{< ref "nginx/releases.md#r19" >}}) | The `expire` parameter of a [key-value](https://nginx.org/en/docs/http/ngx_http_keyval_module.html) pair can be [set](https://nginx.org/en/docs/http/ngx_http_api_module.html#postHttpKeyvalZoneData) or [changed](https://nginx.org/en/docs/http/ngx_http_api_module.html#patchHttpKeyvalZoneKeyValue), the [`/resolvers/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#resolvers_) and [`/http/location_zones/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#http_location_zones_) data were added |
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v4/nginx_api.yaml) for API version 4 | NGINX Plus Release [18]({{< ref "nginx/releases.md#r18" >}}) | The `path` and `method` fields of [nginx error object](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_error) were removed. These fields continue to exist in earlier api versions, but show an empty value |
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v3/nginx_api.yaml) for API version 3 | NGINX Plus Releases [15]({{< ref "nginx/releases.md#r15" >}}), [16]({{< ref "nginx/releases.md#r16" >}}), [17]({{< ref "nginx/releases.md#r17" >}}) | The [`/stream/zone_sync/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#stream_zone_sync_) data were added |
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v2/nginx_api.yaml) for API version 2 | NGINX Plus Release [14]({{< ref "nginx/releases.md#r14" >}}) | The [`drain`](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_upstream_conf_server) parameter was added |
-|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v1/nginx_api.yaml) for API version 1 | NGINX Plus Release [13]({{< ref "nginx/releases.md#r13" >}})| The [`/stream/keyvals/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#stream_keyvals_) data were added |
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v9/nginx_api.yaml) for API version 9 | NGINX Plus Releases [33]({{< ref "/nginx/releases.md#r33" >}}), [34]({{< ref "nginx/releases.md#r34" >}})| The [`/license`](https://nginx.org/en/docs/http/ngx_http_api_module.html#license) data were added|
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v9/nginx_api.yaml) for API version 9 | NGINX Plus Releases [30]({{< ref "nginx/releases.md#r30" >}}), [31]({{< ref "nginx/releases.md#r31" >}}), [32]({{< ref "nginx/releases.md#r32" >}}) | The [`/workers/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#workers_) data were added|
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v8/nginx_api.yaml) for API version 8 | NGINX Plus Releases [27]({{< ref "nginx/releases.md#r27" >}}), [28]({{< ref "nginx/releases.md#r28" >}}), [29]({{< ref "nginx/releases.md#r29" >}}) | SSL statistics for each HTTP [upstream](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_upstream) and stream [upstream](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_stream_upstream), SSL statistics for each HTTP [server zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_server_zone) and stream [server zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_stream_server_zone), extended statistics for [SSL](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_ssl_object) endpoint|
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v7/nginx_api.yaml) for API version 7 | NGINX Plus Releases [25]({{< ref "nginx/releases.md#r25" >}}), [26]({{< ref "nginx/releases.md#r26" >}}),| The `codes` data in `responses` for each HTTP [upstream](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_upstream), [server zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_server_zone), and [location zone](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_location_zone) were added|
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v6/nginx_api.yaml) for API version 6 | NGINX Plus Releases [20]({{< ref "nginx/releases.md#r20" >}}), [21]({{< ref "nginx/releases.md#r21" >}}), [22]({{< ref "nginx/releases.md#r22" >}}), [23]({{< ref "nginx/releases.md#r23" >}}), [24]({{< ref "nginx/releases.md#r24" >}}) | The [`/stream/limit_conns/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#stream_limit_conns_), [`/http/limit_conns/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#http_limit_conns_), and [`/http/limit_reqs/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#http_limit_reqs_) data were added |
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v5/nginx_api.yaml) for API version 5 | NGINX Plus Release [19]({{< ref "nginx/releases.md#r19" >}}) | The `expire` parameter of a [key-value](https://nginx.org/en/docs/http/ngx_http_keyval_module.html) pair can be [set](https://nginx.org/en/docs/http/ngx_http_api_module.html#postHttpKeyvalZoneData) or [changed](https://nginx.org/en/docs/http/ngx_http_api_module.html#patchHttpKeyvalZoneKeyValue), the [`/resolvers/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#resolvers_) and [`/http/location_zones/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#http_location_zones_) data were added |
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v4/nginx_api.yaml) for API version 4 | NGINX Plus Release [18]({{< ref "nginx/releases.md#r18" >}}) | The `path` and `method` fields of [nginx error object](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_error) were removed. These fields continue to exist in earlier api versions, but show an empty value |
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v3/nginx_api.yaml) for API version 3 | NGINX Plus Releases [15]({{< ref "nginx/releases.md#r15" >}}), [16]({{< ref "nginx/releases.md#r16" >}}), [17]({{< ref "nginx/releases.md#r17" >}}) | The [`/stream/zone_sync/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#stream_zone_sync_) data were added |
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v2/nginx_api.yaml) for API version 2 | NGINX Plus Release [14]({{< ref "nginx/releases.md#r14" >}}) | The [`drain`](https://nginx.org/en/docs/http/ngx_http_api_module.html#def_nginx_http_upstream_conf_server) parameter was added |
+|[{{}}OpenAPI v2](/nginx/admin-guide/yaml/v1/nginx_api.yaml) for API version 1 | NGINX Plus Release [13]({{< ref "nginx/releases.md#r13" >}})| The [`/stream/keyvals/`](https://nginx.org/en/docs/http/ngx_http_api_module.html#stream_keyvals_) data were added |
{{}}
diff --git a/content/nginxaas-azure/getting-started/nginx-configuration/nginx-configuration-portal.md b/content/nginxaas-azure/getting-started/nginx-configuration/nginx-configuration-portal.md
index 77a0b75ba..ef07b74aa 100644
--- a/content/nginxaas-azure/getting-started/nginx-configuration/nginx-configuration-portal.md
+++ b/content/nginxaas-azure/getting-started/nginx-configuration/nginx-configuration-portal.md
@@ -32,14 +32,14 @@ NGINXaaS supports Layer 7 HTTP loadbalancing. To configure .com and .net servers
{{}}If you don't see the default configuration, it's likely the deployment was created through a client tool other than the portal (For example, Terraform), or the "Apply default NGINX configuration" was unchecked during the deployment creation process in the portal. You can still proceed with the steps below to provide your own NGINX configuration for the deployment.{{ }}
-1. Select {{< fa "fa fa-plus">}}**New File** to add a file path, then **Confirm**.
+1. Select {{< icon "fa fa-plus">}}**New File** to add a file path, then **Confirm**.
{{}}
| Property | Description |
| -------- | ----------- |
| File path | Each NGINX configuration file can be uniquely identified by a file path (for example, nginx.conf or /etc/nginx/nginx.conf) to align with the intended NGINX configuration file structure. |
| Root file | The root file is the main NGINX configuration file. }}
{{}}If specifying an absolute file path, see the [NGINX Filesystem Restrictions table]({{< ref "/nginxaas-azure/getting-started/nginx-configuration/overview/#nginx-filesystem-restrictions" >}}) for the allowed directories the file can be written to.{{ }}
@@ -146,7 +146,7 @@ http {
1. Select the configuration file you want to delete from the File path list.
-1. Select the delete icon {{< fa "fa fa-trash">}}.
+1. Select the delete icon {{< icon "fa fa-trash">}}.
1. Confirm your action to delete the configuration file.
diff --git a/content/nginxaas-azure/getting-started/ssl-tls-certificates/ssl-tls-certificates-portal.md b/content/nginxaas-azure/getting-started/ssl-tls-certificates/ssl-tls-certificates-portal.md
index 0c27e8ff3..fabd44d4d 100644
--- a/content/nginxaas-azure/getting-started/ssl-tls-certificates/ssl-tls-certificates-portal.md
+++ b/content/nginxaas-azure/getting-started/ssl-tls-certificates/ssl-tls-certificates-portal.md
@@ -24,7 +24,7 @@ Before you begin, refer Azure documentation to [Import a certificate to your Key
1. Select **NGINX certificates** in the left menu.
-1. Select {{< fa "plus">}}**Add certificate**.
+1. Select {{< icon "plus">}}**Add certificate**.
1. Provide the required information:
@@ -72,7 +72,7 @@ Before you begin, refer Azure documentation to [Import a certificate to your Key
1. Select the checkbox next to the certificate you want to edit.
-1. Select {{< fa "pencil">}} **Edit**.
+1. Select {{< icon "pencil">}} **Edit**.
1. Update the Name, Certificate path, Key path fields as needed.
@@ -86,7 +86,7 @@ Before you begin, refer Azure documentation to [Import a certificate to your Key
1. Select the checkbox next to the certificate you want to delete.
-1. Select {{< fa "trash">}}**Delete**.
+1. Select {{< icon "trash">}}**Delete**.
1. Confirm the delete action.
diff --git a/content/nginxaas-azure/quickstart/geoip2.md b/content/nginxaas-azure/quickstart/geoip2.md
index 227b79d1c..e764cd0f9 100644
--- a/content/nginxaas-azure/quickstart/geoip2.md
+++ b/content/nginxaas-azure/quickstart/geoip2.md
@@ -18,7 +18,7 @@ NGINXaaS uses your MaxMind license to download GeoIP2 databases, puts them in th
To enable GeoIP2 you [update your NGINX configuration]({{< ref "/nginxaas-azure/getting-started/nginx-configuration/overview.md">}}) to include your MaxMind license and the relevant NGINX directives.
1. Log into MaxMind and [generate a `GeoIP.conf`](https://dev.maxmind.com/geoip/updating-databases/#2-obtain-geoipconf-with-account-information) file.
-2. Add the `GeoIP.conf` file to your NGINX configuration, using the exact path `/etc/nginx/GeoIP.conf`. The `GeoIP.conf` will be validated, and must include `AccountID`, `LicenseKey`, and `EditionIDs`. Other configuration options in `GeoIP.conf` are ignored. We recommend you enable the **Protected** {{}} toggle button to mark `GeoIP.conf` as a protected file, which will prevent the contents from being read via any Azure client tools.
+2. Add the `GeoIP.conf` file to your NGINX configuration, using the exact path `/etc/nginx/GeoIP.conf`. The `GeoIP.conf` will be validated, and must include `AccountID`, `LicenseKey`, and `EditionIDs`. Other configuration options in `GeoIP.conf` are ignored. We recommend you enable the **Protected** {{}} toggle button to mark `GeoIP.conf` as a protected file, which will prevent the contents from being read via any Azure client tools.
3. Add the `load_module` directive - the modules are available at `modules/ngx_http_geoip2_module.so` or `modules/ngx_stream_geoip2_module.so`.
4. Add `geoip2` directives to your NGINX configuration as desired. The `EditionIDs` from your `GeoIP.conf` are available at `/usr/local/share/GeoIP`
diff --git a/content/nginxaas-azure/quickstart/security-controls/certificates.md b/content/nginxaas-azure/quickstart/security-controls/certificates.md
index 651f76c5c..fdd52cd39 100644
--- a/content/nginxaas-azure/quickstart/security-controls/certificates.md
+++ b/content/nginxaas-azure/quickstart/security-controls/certificates.md
@@ -44,7 +44,7 @@ Next, you can add an SSL/TLS certificate to your key vault by following [Azure's
1. Go to your key vault, `nginxaas-kv`.
1. Select **Certificates** in the left menu.
-1. Select {{< fa "plus">}}**Generate/Import** and provide the following information:
+1. Select {{< icon "plus">}}**Generate/Import** and provide the following information:
{{}}
| Field | Description |
@@ -68,7 +68,7 @@ In order for your NGINXaaS deployment to access your key vault, it must have an
1. Under **System assigned**, ensure the status is set to "On".
{{}} When you create a deployment through the Azure portal, a system-assigned managed identity is automatically enabled for your deployment. {{ }}
1. Under **System assigned**, select **Azure role assignments**.
-1. Select {{< fa "plus">}}**Add role assignment** and provide the following information:
+1. Select {{< icon "plus">}}**Add role assignment** and provide the following information:
{{}}
| Field | Description |
@@ -87,7 +87,7 @@ Now, you can add your SSL/TLS certificate from your key vault to your NGINXaaS d
1. Go to your NGINXaaS deployment.
1. Select **NGINX certificates** in the left menu.
-1. Select {{< fa "plus">}}**Add certificate** and provide the following information:
+1. Select {{< icon "plus">}}**Add certificate** and provide the following information:
{{}}
| Field | Description |
|---------------------------- | ---------------------------- |
@@ -168,7 +168,7 @@ If you want to disable public access to your key vault, you can configure a [Net
1. Follow [Azure's documentation on prerequisites](https://learn.microsoft.com/en-us/azure/private-link/create-network-security-perimeter-portal#prerequisites) to ensure you are registed to create an NSP.
1. In the Search box, enter **Network Security Perimeters** and select **Network Security Perimeters** from the search results.
-1. Select {{< fa "plus">}}**Create**.
+1. Select {{< icon "plus">}}**Create**.
1. In the **Basics** tab, provide the following information:
{{}}
| Field | Description |
@@ -179,9 +179,9 @@ If you want to disable public access to your key vault, you can configure a [Net
| Region | Select the region you want to deploy to. Refer to any [regional limitations](https://learn.microsoft.com/en-us/azure/private-link/network-security-perimeter-concepts#regional-limitations) NSP has while in public preview. |
| Profile name | Leave the profile name as the default `defaultProfile`. |
{{ }}
-1. In the **Resources** tab, select {{< fa "plus">}}**Add**.
+1. In the **Resources** tab, select {{< icon "plus">}}**Add**.
1. Search for your key vault, `nginxaas-kv`, select it, and click **Select**.
-1. In the **Inbound access rules** tab, select {{< fa "plus">}}**Add** and provide the following information:
+1. In the **Inbound access rules** tab, select {{< icon "plus">}}**Add** and provide the following information:
{{}}
| Field | Description |
|---------------------------- | ---------------------------- |
@@ -198,4 +198,4 @@ By default, the key vault will be associated to the NSP in [Learning mode](https
1. Select the `nginxaas-kv` resource association.
1. Select **Change access mode**, set to **Enforced**, and select **Apply**.
-{{}} If you are using the Azure portal to add certificates, you will also need to add an inbound access rule to allow your IP address, so the portal can list the certificates in your key vault. {{ }}
\ No newline at end of file
+{{}} If you are using the Azure portal to add certificates, you will also need to add an inbound access rule to allow your IP address, so the portal can list the certificates in your key vault. {{ }}
diff --git a/content/nim/deploy/docker/deploy-nginx-instance-manager-docker-compose.md b/content/nim/deploy/docker/deploy-nginx-instance-manager-docker-compose.md
index 1e451340b..b1f9523bb 100644
--- a/content/nim/deploy/docker/deploy-nginx-instance-manager-docker-compose.md
+++ b/content/nim/deploy/docker/deploy-nginx-instance-manager-docker-compose.md
@@ -31,9 +31,9 @@ Before you begin, make sure you have the following:
- A JSON Web Token (JWT) from your [MyF5 subscriptions page](https://my.f5.com/manage/s/subscriptions). This is the same token used for NGINX Plus.
- The right `docker-compose.yaml` file for your setup:
- For **standard mode** (with metrics and dashboards):
- {{}} {{}}
+ {{}} {{}}
- For **lightweight mode** (no ClickHouse, no metrics):
- {{}} {{}}
+ {{}} {{}}
{{< note >}} If you're not sure which one to use, start with lightweight mode. You can always switch later by changing the Compose file and setting `ENABLE_METRICS: "true"`.{{< /note >}}
@@ -337,4 +337,4 @@ Run the backup command to capture the current state:
docker exec nim-nim-1 nim-backup
```
-This creates a `.tgz` file inside the container under `/data/backup/`, which you can extract as described in the [Backup](#backup) section.
\ No newline at end of file
+This creates a `.tgz` file inside the container under `/data/backup/`, which you can extract as described in the [Backup](#backup) section.
diff --git a/content/nim/deploy/infrastructure-as-code/build-and-deploy.md b/content/nim/deploy/infrastructure-as-code/build-and-deploy.md
index f54fc9dbd..aed40e279 100644
--- a/content/nim/deploy/infrastructure-as-code/build-and-deploy.md
+++ b/content/nim/deploy/infrastructure-as-code/build-and-deploy.md
@@ -18,7 +18,7 @@ The deployment process has two stages:
- Generate an image using Packer.
- Deploy the image using Terraform.
-{{< call-out "tip" "Open-Source Project on GitHub" "fa-brands fa-github" >}}
+{{< call-out "tip" "Open-Source Project on GitHub" >}}
The steps in this guide refer to the [NGINX Instance Manager Infrastructure as Code (IAC)](https://github.com/nginxinc/nginx-management-suite-iac) project on GitHub.
{{< /call-out >}}
diff --git a/content/nim/deploy/infrastructure-as-code/configuration.md b/content/nim/deploy/infrastructure-as-code/configuration.md
index 51c43dee3..481a7d30b 100644
--- a/content/nim/deploy/infrastructure-as-code/configuration.md
+++ b/content/nim/deploy/infrastructure-as-code/configuration.md
@@ -15,7 +15,7 @@ This guide explains how to install F5 NGINX Instance Manager using the open-sour
With Ansible, you can automate and replicate your installation across multiple environments.
-{{< call-out "tip" "Open-Source Project on GitHub" "fa-brands fa-github" >}}
+{{< call-out "tip" "Open-Source Project on GitHub" >}}
The steps in this guide refer to the [Ansible NGINX Instance Manager Role](https://github.com/nginxinc/ansible-role-nginx-management-suite) project on GitHub.
{{< /call-out >}}
diff --git a/content/nim/deploy/vm-bare-metal/install.md b/content/nim/deploy/vm-bare-metal/install.md
index bd104a3ac..f06b29897 100644
--- a/content/nim/deploy/vm-bare-metal/install.md
+++ b/content/nim/deploy/vm-bare-metal/install.md
@@ -30,7 +30,7 @@ Follow these steps to prepare for installing NGINX Instance Manager:
- **Download the installation script**:
- {{}} {{}}
+ {{}} {{}}
- **Download the certificate and private key** (see the steps [below](#download-cert-key)):
Use the certificate and private key for NGINX Instance Manager (the same files used for NGINX Plus).
@@ -91,7 +91,7 @@ Download the certificate and private key required for NGINX Instance Manager. Th
If you haven’t already downloaded the script, you can download it here:
-{{}} {{}}
+{{}} {{}}
### Prepare your system for installation
diff --git a/content/nim/disconnected/add-license-disconnected-deployment.md b/content/nim/disconnected/add-license-disconnected-deployment.md
index 61926dc6e..e1ec9fb32 100644
--- a/content/nim/disconnected/add-license-disconnected-deployment.md
+++ b/content/nim/disconnected/add-license-disconnected-deployment.md
@@ -51,7 +51,7 @@ To add a license and submit the initial usage report in a disconnected environme
-1. {{}}[Download license_usage_offline.sh](/scripts/license_usage_offline.sh).
+1. {{}}[Download license_usage_offline.sh](/scripts/license_usage_offline.sh).
1. Run the following command to allow the script to run:
```bash
@@ -65,7 +65,7 @@ To add a license and submit the initial usage report in a disconnected environme
-j .jwt \
-i \
-u admin \
- -p \
+ -p \
-s initial
```
@@ -235,7 +235,3 @@ To upload the the usage acknowledgement:
{{}}
-
-
-
-
diff --git a/content/nim/disconnected/offline-install-guide-manual.md b/content/nim/disconnected/offline-install-guide-manual.md
index f86873880..6cc81f7f6 100644
--- a/content/nim/disconnected/offline-install-guide-manual.md
+++ b/content/nim/disconnected/offline-install-guide-manual.md
@@ -35,7 +35,7 @@ To complete the steps in this guide, you need to download the NGINX Instance Man
Local dependencies are common Linux packages like `curl` or `openssl`, which most Linux distributions include by default. When installing NGINX Instance Manager, your package manager will automatically install these dependencies. Without internet access, ensure your package manager can use a local package repository, such as a distribution DVD/ISO image or internal network mirror. Check your Linux distribution's documentation for details.
-{{< call-out "note" "RedHat on AWS" "fa-brands fa-aws" >}}If you're using AWS and can't attach remote or local RedHat package repositories, download the necessary packages on another RedHat machine and copy them to your target machine. Use the `yumdownloader` utility for this task:
+{{< call-out "note" "RedHat on AWS" >}}If you're using AWS and can't attach remote or local RedHat package repositories, download the necessary packages on another RedHat machine and copy them to your target machine. Use the `yumdownloader` utility for this task:
.
{{}}
@@ -47,7 +47,7 @@ To download external dependencies:
1. Download the `fetch-external-dependencies.sh` script:
- {{}} {{}}
+ {{}} {{}}
2. Run the script to download the external dependencies for your specific Linux distribution:
@@ -202,4 +202,4 @@ sudo systemctl restart nms-dpm
## Next steps
-- [Add NGINX Open Source and NGINX Plus instances to NGINX Instance Manager]({{< ref "nim/nginx-instances/add-instance.md" >}})
\ No newline at end of file
+- [Add NGINX Open Source and NGINX Plus instances to NGINX Instance Manager]({{< ref "nim/nginx-instances/add-instance.md" >}})
diff --git a/content/nim/disconnected/offline-install-guide.md b/content/nim/disconnected/offline-install-guide.md
index c8dedfee6..5dd212173 100644
--- a/content/nim/disconnected/offline-install-guide.md
+++ b/content/nim/disconnected/offline-install-guide.md
@@ -62,7 +62,7 @@ Download the SSL certificate and private key required for NGINX Instance Manager
### Download the installation script
-{{}} {{}}
+{{}} {{}}
## Package NGINX Instance Manager and dependencies for offline installation
@@ -210,4 +210,4 @@ sudo systemctl restart nms-dpm
## Next steps
-- [Add NGINX Open Source and NGINX Plus instances to NGINX Instance Manager]({{< ref "nim/nginx-instances/add-instance.md" >}})
\ No newline at end of file
+- [Add NGINX Open Source and NGINX Plus instances to NGINX Instance Manager]({{< ref "nim/nginx-instances/add-instance.md" >}})
diff --git a/content/nim/disconnected/report-usage-disconnected-deployment.md b/content/nim/disconnected/report-usage-disconnected-deployment.md
index 9fecb335b..a3913a058 100644
--- a/content/nim/disconnected/report-usage-disconnected-deployment.md
+++ b/content/nim/disconnected/report-usage-disconnected-deployment.md
@@ -47,7 +47,7 @@ To submit a usage report in a disconnected environment, use the provided `licens
-1. {{}}[Download license_usage_offline.sh](/scripts/license_usage_offline.sh).
+1. {{}}[Download license_usage_offline.sh](/scripts/license_usage_offline.sh).
1. Run the following command to allow the script to run:
```bash
diff --git a/content/nim/nginx-app-protect/security-monitoring/give-access-to-security-monitoring-dashboards.md b/content/nim/nginx-app-protect/security-monitoring/give-access-to-security-monitoring-dashboards.md
index 6d29edf1a..a3e092a37 100644
--- a/content/nim/nginx-app-protect/security-monitoring/give-access-to-security-monitoring-dashboards.md
+++ b/content/nim/nginx-app-protect/security-monitoring/give-access-to-security-monitoring-dashboards.md
@@ -36,7 +36,7 @@ Make sure you complete these steps:
| Module(s) | Feature(s) | Access | Description |
|-----------------------------------|-----------------------|----------------------------|----------------------------------------------------------------------------------------------------------|
| Instance Manager
Security Monitoring | Analytics
Security Monitoring | `READ`
`READ` | Gives read-only access to Security Monitoring dashboards. Users cannot access NGINX Instance Manager or Settings. | - | Instance Manager
Security Monitoring
Settings | Analytics
Security Monitoring
User Management | `READ`
`READ`
`CREATE`, `READ`, `UPDATE` | Lets users view dashboards and manage accounts and roles.
{{< fa "lightbulb" >}} Best for "super-users" who manage dashboard access. Does not allow deleting accounts. | + | Instance Manager
Security Monitoring
Settings | Analytics
Security Monitoring
User Management | `READ`
`READ`
`CREATE`, `READ`, `UPDATE` | Lets users view dashboards and manage accounts and roles.
{{< icon "lightbulb" >}} Best for "super-users" who manage dashboard access. Does not allow deleting accounts. | {{ }}
@@ -62,4 +62,4 @@ Assign the Security Monitoring role to users or groups.
### Assign the role to user groups
-{{< include "nim/rbac/assign-roles-to-user-groups.md" >}}
\ No newline at end of file
+{{< include "nim/rbac/assign-roles-to-user-groups.md" >}}
diff --git a/content/nim/system-configuration/configure-forward-proxy.md b/content/nim/system-configuration/configure-forward-proxy.md
index f0d1bda26..51746e52f 100644
--- a/content/nim/system-configuration/configure-forward-proxy.md
+++ b/content/nim/system-configuration/configure-forward-proxy.md
@@ -127,7 +127,7 @@ kubectl edit cm nms-conf -n
If you’re deploying NGINX Instance Manager with Docker Compose, update the `docker-compose.yaml` file to configure a forward proxy.
1. **Before you begin**: Follow the [Docker Compose deployment guide]({{< ref "nim/deploy/docker/deploy-nginx-instance-manager-docker-compose.md" >}}) to set up Docker for the NGINX container registry. The deployment guide also covers additional environment variables you may want to consider before deployment.
-2. {{}} {{}}
+2. {{}} {{}}
3. Update `docker-compose.yaml` with the proxy settings:
Modify the `services.nim.environment` section to include the proxy configuration:
diff --git a/content/nim/system-configuration/secure-traffic.md b/content/nim/system-configuration/secure-traffic.md
index 3e361c605..5a95b9905 100644
--- a/content/nim/system-configuration/secure-traffic.md
+++ b/content/nim/system-configuration/secure-traffic.md
@@ -194,7 +194,7 @@ To generate the necessary certificates, follow these steps. You can modify these
}} {{}}
+ {{}} {{}}
``` yaml
[req]
diff --git a/content/nms/acm/getting-started/add-api-gateway.md b/content/nms/acm/getting-started/add-api-gateway.md
index d04a0aec8..0af2db5d9 100644
--- a/content/nms/acm/getting-started/add-api-gateway.md
+++ b/content/nms/acm/getting-started/add-api-gateway.md
@@ -56,7 +56,7 @@ Use the appropriate example below to deploy an API Gateway with either HTTP, HTT
### HTTP
-> {{< fa "lightbulb" >}} Use this example to get up and running quickly in a demo environment.
+> {{< icon "lightbulb" >}} Use this example to get up and running quickly in a demo environment.
{{}}
@@ -91,7 +91,7 @@ Use the appropriate example below to deploy an API Gateway with either HTTP, HTT
To deploy a cluster that uses HTTPS for secure inbound communication, you'll add the **TLS Inbound** policy.
Because this is done at the Infrastructure level, this is considered a "Global Policy".
-> {{< fa "lightbulb" >}} You need to provide a valid TLS server certificate and key in this API call.
+> {{< icon "lightbulb" >}} You need to provide a valid TLS server certificate and key in this API call.
{{}}
Need to add requirements for sending this info? Base64 encoding required?
@@ -140,7 +140,7 @@ Need to add requirements for sending this info? Base64 encoding required?
To deploy a cluster that uses HTTP2 for secure inbound communication, you'll add the **TLS Inbound** policy.
Because this is done at the Infrastructure level, this is considered a "Global Policy".
-> {{< fa "lightbulb" >}} You need to provide a valid TLS server certificate and key in this API call.
+> {{< icon "lightbulb" >}} You need to provide a valid TLS server certificate and key in this API call.
{{}}
@@ -224,4 +224,3 @@ Try sending traffic to the hostname you configured for the API Gateway. Send a P
| GET | `/infrastructure/workspaces/{{infraWorkspaceName}}/environments/{{environmentName}}?includes=instances&includes=status`|
{{ }}
-
diff --git a/content/nms/acm/getting-started/add-devportal.md b/content/nms/acm/getting-started/add-devportal.md
index ffee41ea3..6ee337534 100644
--- a/content/nms/acm/getting-started/add-devportal.md
+++ b/content/nms/acm/getting-started/add-devportal.md
@@ -41,7 +41,7 @@ Use the appropriate example below to deploy an HTTP or HTTPS Developer Portal.
### HTTP
-> {{< fa "lightbulb" >}} Use this example to get up and running quickly in a demo environment.
+> {{< icon "lightbulb" >}} Use this example to get up and running quickly in a demo environment.
{{}}
@@ -76,7 +76,7 @@ Use the appropriate example below to deploy an HTTP or HTTPS Developer Portal.
To deploy a cluster that uses HTTPS for secure inbound communication, you'll add the **TLS Inbound** policy.
Because this is done at the Infrastructure level, this is considered a "Global Policy".
-> {{< fa "lightbulb" >}} You need to provide your TLS server certificate and key as base64-encoded strings in this API call.
+> {{< icon "lightbulb" >}} You need to provide your TLS server certificate and key as base64-encoded strings in this API call.
{{}}
@@ -146,7 +146,7 @@ SSH access to the host and `sudo` permissions are required.
The NGINX Management Suite management plane host uses the Developer Portal's hostname to communicate with the Dev Portal.
You’ll need to update your DNS resolver settings with the Developer Portal's internal hostname.
-> {{< fa "lightbulb" >}} The internal hostname is the hostname that you provided for the Developer Portal, prefixed with `acm.`.
+> {{< icon "lightbulb" >}} The internal hostname is the hostname that you provided for the Developer Portal, prefixed with `acm.`.
> For example: `acm.dev-portal.io`
Next, open the Developer Portal in a browser window and make sure the portal loads.
@@ -170,7 +170,7 @@ Because these settings are applied at the Infrastructure level, they are conside
Note that many fields in the example JSON payload -- including the logo image and Markdown documents -- are base64-encoded.
-**Example JSON payload**: {{< fa "download" >}} {{< link "/acm/customize-devportal.json" "customize-devportal.json" >}}
+**Example JSON payload**: {{< icon "download" >}} {{< link "/acm/customize-devportal.json" "customize-devportal.json" >}}
Before you move on to the next guide, open the Dev Portal in your browser to view the changes.
You should see the default Dev Portal replaced by the custom settings.
diff --git a/content/nms/acm/how-to/devportals/installation/devportal-helm-chart.md b/content/nms/acm/how-to/devportals/installation/devportal-helm-chart.md
index 1ad7e99db..316b5c53f 100644
--- a/content/nms/acm/how-to/devportals/installation/devportal-helm-chart.md
+++ b/content/nms/acm/how-to/devportals/installation/devportal-helm-chart.md
@@ -115,7 +115,7 @@ Create a Dockerfile similar to the following example:
}} {{}}
+ {{}} {{}}
4. To download the NGINX Plus and njs dependencies, run the `fetch-external-acm-dataplane-dependencies.sh` script. As parameters, specify your Linux distribution and the location of your `nginx-repo.crt` and `nginx-repo.key` files.
diff --git a/content/nms/acm/how-to/infrastructure/customize-devportal.md b/content/nms/acm/how-to/infrastructure/customize-devportal.md
index b7c9a31e7..a9e5f5458 100644
--- a/content/nms/acm/how-to/infrastructure/customize-devportal.md
+++ b/content/nms/acm/how-to/infrastructure/customize-devportal.md
@@ -162,7 +162,7 @@ To edit the **Get Started** steps:
1. Enter your desired **Title** (required), **Description** (required), icon, and **Alt Text** for each of the four steps.
1. Select **Save Changes**.
-> {{< fa "fa-solid fa-lightbulb" >}} At this point, we recommend selecting **Save and Publish** to save any customizations you've made.
+> {{< icon "fa-solid fa-lightbulb" >}} At this point, we recommend selecting **Save and Publish** to save any customizations you've made.
> Verify that the changes have been applied, then move on to adding your [**Documentation**](#add-documentation).
### Documentation {#add-documentation}
diff --git a/content/nms/acm/how-to/infrastructure/manage-api-infrastructure.md b/content/nms/acm/how-to/infrastructure/manage-api-infrastructure.md
index a8f01d8aa..93b47c51a 100644
--- a/content/nms/acm/how-to/infrastructure/manage-api-infrastructure.md
+++ b/content/nms/acm/how-to/infrastructure/manage-api-infrastructure.md
@@ -184,11 +184,10 @@ Take the steps below to add an NGINX instance to an API Gateway.
{{ }}
-> {{< fa "fa-solid fa-circle-question" >}} **Lost your install command?**
+> {{< icon "fa-solid fa-circle-question" >}} **Lost your install command?**
>
> Don't worry! You can take the steps below to recover it:
>
> 1. In the API Connectivity Manager user interface, go to **Infrastructure > Environments > \**.
> 1. Click anywhere in the row of the Cluster that you want to add an instance to.
> 1. The **Onboarding Commands** will be shown in the cluster details drawer.
-
diff --git a/content/nms/acm/how-to/install-acm-offline.md b/content/nms/acm/how-to/install-acm-offline.md
index 962a4efeb..74189e448 100644
--- a/content/nms/acm/how-to/install-acm-offline.md
+++ b/content/nms/acm/how-to/install-acm-offline.md
@@ -152,7 +152,7 @@ The API Connectivity Manager data plane requires [NGINX Plus R24](https://docs.n
3. Select the following link to download the `fetch-external-acm-dataplane-dependencies.sh` script. This script downloads the necessary NGINX Plus and njs packages to a `tar.gz` archive.
- {{}} {{}}
+ {{}} {{}}
4. To download the NGINX Plus and njs dependencies, run the `fetch-external-acm-dataplane-dependencies.sh` script. As parameters, specify your Linux distribution and the location of your `nginx-repo.crt` and `nginx-repo.key` files.
diff --git a/documentation/nginx-org-source.md b/documentation/nginx-org-source.md
new file mode 100644
index 000000000..e7e9bbd28
--- /dev/null
+++ b/documentation/nginx-org-source.md
@@ -0,0 +1,45 @@
+# nginx.org content
+
+This document describes the process by which https://github.com/nginx/nginx.org are ingested by the `nginx/documentation` repository, and rendered as markdown.
+
+## Source of truth
+The https://github.com/nginx/nginx.org repository remains the source of truth for a subset of content in `/content/nginx`. Primarily, this includes is the `module reference`, and the https://github.com/nginx/nginx.org/blob/main/yaml/nginx_api.yaml.
+
+Any modifications to these autogenerated files will be blocked during the pull request process.
+If modifications are required, they will be made in the source xml in https://github.com/nginx/nginx.org repository.
+
+All files that are autogenerated from this source, will have the warning:
+
+```md
+********************************************************************************
+🛑 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
+********************************************************************************
+```
+
+## Markdown generation flow
+
+A GitHub Action running as a cron job in the `nginx/documentation` repository detects changes in the documentation within `nginx/nginx.org`, generates new markdown files when changes are found, and creates a PR with these changes.
+
+Only PRs generated by this GitHub Action can be merged.
+
+The markdown files are generated using a markdown-specific XSLT file, which targets only the XML sources intended for inclusion in the nginx/documentation repository.
+
+```mermaid
+flowchart TD
+ Start([Cron Job Triggered]) --> CheckChanges{Changes detected in 'en' docs of nginx/nginx.org?}
+ CheckChanges -- Yes --> CloneRepo[Clone nginx/nginx.org repository]
+ CloneRepo --> RunMake["Execute make target: 'make hugo-md'"]
+ RunMake --> MoveFiles["Move generated markdown files to '/content/nginx' directory"]
+ MoveFiles --> OpenPR["Create PR in nginx/documentation repository"]
+ OpenPR --> Finish([End])
+
+ CheckChanges -- No --> FinishNoAction([End - No updates detected])
+
+ style Finish stroke:#27ae60,stroke-width:2px
+ style OpenPR stroke:#2980b9,stroke-width:2px
+ style CheckChanges stroke:#7f8c8d,stroke-width:2px
+```
diff --git a/layouts/catalogs/single.html b/layouts/catalogs/single.html
index ca27eff9f..b1fb68f10 100644
--- a/layouts/catalogs/single.html
+++ b/layouts/catalogs/single.html
@@ -1,10 +1,7 @@
{{ define "main" }}
{{< fa "brands fa-freebsd" >}} Uninstall NGINX Agent on FreeBSD
+Uninstall NGINX Agent on FreeBSD
### Uninstall NGINX Agent on FreeBSD diff --git a/content/nginx/admin-guide/monitoring/live-activity-monitoring.md b/content/nginx/admin-guide/monitoring/live-activity-monitoring.md index 55474230f..e1051af0c 100644 --- a/content/nginx/admin-guide/monitoring/live-activity-monitoring.md +++ b/content/nginx/admin-guide/monitoring/live-activity-monitoring.md @@ -521,16 +521,16 @@ To enable the Swagger UI: |OpenAPI YAML File/API Version | NGINX Plus Version | Changes | | ---| --- | --- | -|[{{- The first file created will be the root file by default. You can designate a different root file if you have more than a single configuration file in your deployment.
- The root file is designated with a {{< golden-star >}} icon on the portal.
- To protect a file, enable the **Protected** {{
}} toggle button. - You cannot access the file contents of a protected file saved to the NGINX configuration, but you can view its metadata, such as the SHA-256 hash of the file contents.
- You can provide new contents for an existing protected file using the **Overwrite** link or resubmit it without having to provide the file contents again.
- To modify the file path of a protected file or convert it to a regular file, delete the original file and create a new one.
- A protected file is designated with a {{
}} icon on the portal.
- To protect a file, enable the **Protected** {{
}} toggle button. - You cannot access the file contents of a protected file saved to the NGINX configuration, but you can view its metadata, such as the SHA-256 hash of the file contents.
- You can provide new contents for an existing protected file using the **Overwrite** link or resubmit it without having to provide the file contents again.
- To modify the file path of a protected file or convert it to a regular file, delete the original file and create a new one.
- A protected file is designated with a {{
}} icon on the portal.
-1. {{
-1. {{
Security Monitoring | Analytics
Security Monitoring | `READ`
`READ` | Gives read-only access to Security Monitoring dashboards. Users cannot access NGINX Instance Manager or Settings. | - | Instance Manager
Security Monitoring
Settings | Analytics
Security Monitoring
User Management | `READ`
`READ`
`CREATE`, `READ`, `UPDATE` | Lets users view dashboards and manage accounts and roles.
{{< fa "lightbulb" >}} Best for "super-users" who manage dashboard access. Does not allow deleting accounts. | + | Instance Manager
Security Monitoring
Settings | Analytics
Security Monitoring
User Management | `READ`
`READ`
`CREATE`, `READ`, `UPDATE` | Lets users view dashboards and manage accounts and roles.
{{< icon "lightbulb" >}} Best for "super-users" who manage dashboard access. Does not allow deleting accounts. | {{
ca.cnf
- {{Example Dockerfile
- {{< fa "download" >}} {{< link "/acm/containers/devportal/Dockerfile" "Download example Dockerfile" >}} + {{< icon "download" >}} {{< link "/acm/containers/devportal/Dockerfile" "Download example Dockerfile" >}} ```Dockerfile FROM ubuntu:focal @@ -193,7 +193,7 @@ Create a Dockerfile similar to the following example:Example entrypoint.sh
- {{< fa "download" >}} {{< link "/acm/containers/devportal/entrypoint.sh" "Download example entrypoint.sh file" >}} + {{< icon "download" >}} {{< link "/acm/containers/devportal/entrypoint.sh" "Download example entrypoint.sh file" >}} ```bash #!/bin/bash @@ -451,4 +451,3 @@ This configuration is recommended for proof of concept installations and not for ### Deploy Developer Portal using TLS for the backend API service {{< include "installation/helm/acm/dev-portal-helm-configurations/configure-devportal-helm-api-mtls.md" >}} - diff --git a/content/nms/acm/how-to/devportals/installation/install-devportal-offline.md b/content/nms/acm/how-to/devportals/installation/install-devportal-offline.md index 2d3f58eeb..899d8dcd9 100644 --- a/content/nms/acm/how-to/devportals/installation/install-devportal-offline.md +++ b/content/nms/acm/how-to/devportals/installation/install-devportal-offline.md @@ -34,7 +34,7 @@ To install NGINX Plus and njs, take the following steps on the Developer Portal 3. Select the following link to download the `fetch-external-acm-dataplane-dependencies.sh` script. This script downloads the necessary NGINX Plus and njs packages to a `tar.gz` archive. - {{
-
-
+
{{ .Content }}
@@ -14,4 +11,3 @@
{{end }}
{{ end }}
-
diff --git a/layouts/index.html b/layouts/index.html
index e09d14f66..303e1dfad 100644
--- a/layouts/index.html
+++ b/layouts/index.html
@@ -1,426 +1,3 @@
{{ define "main" }}
-
+
-
-
-{{/* mf homepage */}}
-
-
-
-
-
-
- {{ if eq .Title "NGINX Product Documentation" }}
-
-
-NGINX Product Documentation
- {{ end}} {{ if .Description }} -{{ .Description | markdownify }}
- {{ end}} {{ if .Content }} -{{ .Content }}
- {{ end }} -
-
-
-
-
-NGINX One
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-NGINX App Protect
-
-
-
-
-
-
-
-
-
-
-
-NGINX as a Service
-
-
-
-
-
-
-
-
-
-
-
-
- More NGINX Products
-
-
-
-{{ end }}
+{{ partial "homepage.html" . }}
+{{end}}
diff --git a/layouts/shortcodes/catalogs-dimensions.html b/layouts/shortcodes/catalogs-dimensions.html
index 1b38e46f4..2b88e9701 100644
--- a/layouts/shortcodes/catalogs-dimensions.html
+++ b/layouts/shortcodes/catalogs-dimensions.html
@@ -1,13 +1,12 @@
{{/* This shortcode **requires** that the document uses the _default/catalogs.html layout */}}
-
-
-
-
- NGINX Product Documentation
-
-
- - NGINX One -
- -
-
-
-
-
-
-
-
- 
-
-
- - NGINX One Console -
-
- Monitor your infrastructure, address security vulnerabilities, and assess the health of your NGINX fleet, all from a single console.
-
-
-
-
-
-
-
-
-
- 
-
-
-
- NGINX Plus
-
-
- The all-in-one load balancer, reverse proxy, web server, content cache, and API gateway.
-
-
-
-
-
-
-
-
-
- 
-
-
-
- NGINX Instance Manager
-
-
- Track and control NGINX Open Source and NGINX Plus instances.
-
-
-
-
-
-
-
-
-
- 
-
-
-
- NGINX Ingress Controller
-
-
- Kubernetes traffic management with API gateway, identity, and observability features
-
-
-
-
-
-
-
-
-
- 
-
-
-
- NGINX Gateway Fabric
-
-
- Next generation Kubernetes connectivity using the Gateway API.
-
-
-
-
-
-
-
-
-
- 
-
-
-
- NGINX Open Source
-
-
- The open source all-in-one load balancer, content cache, and web server
-
-
-
-
-
-
-
-
-
-
-
-
-
- NGINX Agent
-
-
- A daemon providing observability data and remote configuration for NGINX Open Source and NGINX Plus instances
-
-
-
-
-
-
-
-
-
-
-
-
- Subscription Licensing & Solutions
-
-
- Stay compliant with your NGINX subscription licenses and see how you can use NGINX One to build secure, scalable, and high-performing applications and APIs.
-
-
-
-
-
- NGINX App Protect
-
-
-
-
-
-
-
-
-
-
-
- 
-
-
-
- NGINX App Protect WAF
-
-
- Lightweight, high-performance, advanced protection against Layer 7 attacks on your apps and APIs
-
-
-
-
-
-
-
- 
-
-
-
- NGINX App Protect DoS
-
-
- Defend, adapt, and mitigate against Layer 7 denial-of-service attacks on your apps and APIs
-
-
-
-
-
-
- NGINX as a Service
-
-
-
-
-
-
-
-
-
-
- 
-
-
-
- NGINX as a Service for Azure
-
-
- Infrastructure-as-a-Service (IaaS) version of NGINX Plus for your Microsoft Azure application stack
-
-
-
-
-
- More NGINX Products
-
-
-
-
-
-
-
-
-
-
-
-
-
- NGINX Unit
-
-
- Dynamic app server that can run beside NGINX, NGINX Plus, or on its own
-
-