Merge branch 'main' into fix-napdos-rocky9-installation

Author: ADubhlaoich

.github/pull_request_template.md

@@ -14,7 +14,7 @@
 [//]: # "If the changes were defined by a GitHub issue, reference it using keywords."
 [//]: # "https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests"
 
-[//]: # "Do not like to any internal, non-public resources. This includes internal repository issues or anything in an intranet."
+[//]: # "Do not link to any internal, non-public resources. This includes internal repository issues or anything in an intranet."
 [//]: # "You can make reference to internal discussions without linking to them: see 'Referencing internal information'."
 [//]: # "https://github.com/nginx/documentation/blob/main/documentation/closed-contributions.md#referencing-internal-information"
 

.github/workflows/build-push.yml

@@ -115,51 +115,4 @@ jobs:
             }
     env:
       SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL_FRIENDS_OF_DOCS }}
-      PREVIEW_URL: ${{ needs.call-docs-build-push.outputs.PREVIEW_URL }}
-
-
-  lighthouseci:
-    if: github.event.pull_request
-    needs: call-docs-build-push
-    runs-on: ubuntu-22.04
-    steps:
-      - uses: actions/checkout@v5
-        with:
-          ref: ${{ github.event.workflow_run.head_branch }}
-      - uses: actions/setup-node@v5
-        with:
-          node-version: 18
-      - name: Installing packages
-        run: npm install
-      - name: Generating lighthouse reports for PR and main...
-        run: | 
-            node lighthouse-script.js
-      - name: Compare the artifacts for negative differences in performance
-        continue-on-error: true
-        run: |
-            FIELDS=("performance" "accessibility") 
-            for FIELD in "${FIELDS[@]}"; do
-                PR_VALUE=$(cat lighthouse-reports/pr-report.json | jq -r ".categories.$FIELD.score")
-                MAIN_VALUE=$(cat lighthouse-reports/main-report.json | jq -r ".categories.$FIELD.score")
-                echo "$FIELD: PR - $PR_VALUE | Main - $MAIN_VALUE"
-
-                if [ $FIELD = "performance" ]; then  
-                  LOWER_BOUND=$(echo "$MAIN_VALUE - 0.05" | bc)
-                  UPPER_BOUND=$(echo "$MAIN_VALUE + 0.05" | bc)
-                  if (( $(echo "$PR_VALUE < $LOWER_BOUND" | bc -l) || $(echo "$PR_VALUE > $UPPER_BOUND" | bc -l) )); then
-                      echo "Error: $FIELD score in PR ($PR_VALUE) is less than in MAIN ($MAIN_VALUE)"
-                      exit 1
-                  fi
-                else
-                  if (( $(echo "$PR_VALUE < $MAIN_VALUE" | bc -l) )); then
-                    echo "Error: $FIELD score in PR ($PR_VALUE) is less than in MAIN ($MAIN_VALUE)"
-                    exit 1
-                  fi
-                fi
-            done
-      - uses: actions/upload-artifact@v4
-        if: ${{ !cancelled() }}
-        with:
-            name: lighthouse-reports
-            path: lighthouse-reports/
-            retention-days: 30
+      PREVIEW_URL: ${{ needs.call-docs-build-push.outputs.PREVIEW_URL }}

.github/workflows/notification.yml

@@ -5,6 +5,7 @@ on:
     workflows:
       - "QE LinkChecker"
       - "Check for Broken Links"
+      - "UI validation on prod"
     types: [completed]
 
 permissions:

.github/workflows/playwright.yml

@@ -0,0 +1,32 @@
+name: UI validation on prod
+on: 
+  workflow_dispatch:
+  schedule:
+    - cron: "0 * * * *"
+
+jobs:
+  run-playwright-tests:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - uses: actions/setup-node@v4
+      with:
+        node-version: lts/*
+    - name: Install dependencies
+      run: npm ci
+    - name: Install Playwright Browsers
+      run: npx playwright install --with-deps
+    - name: Run Playwright tests
+      run: npx playwright test --retries=2
+    - uses: actions/upload-artifact@v4
+      if: ${{ !cancelled() }}
+      with:
+        name: playwright-report
+        path: tests/playwright-report/
+        retention-days: 30
+    - uses: actions/upload-artifact@v4
+      if: ${{ !cancelled() }}
+      with:
+        name: test-results
+        path: tests/test-results/
+        retention-days: 30

.gitignore

@@ -35,11 +35,13 @@ resources/
 .netlify/plugins/*
 .netlify/
 
-# Local Lighthouse artifacts
-lighthouse-reports
-
 *.pyc
 build
 *.swp
 *.mo
 node_modules
+
+# Playwright
+/coverage
+*/test-results
+*/playwright-report

content/nginx/admin-guide/basic-functionality/managing-configuration-files.md

@@ -9,9 +9,9 @@ type:
 - how-to
 ---
 
-NGINX and NGINX Plus are similar to other services in using a text‑based configuration file with a precise format. By default the file is named **nginx.conf** and for NGINX Plus is placed in the `**/etc/nginx**` directory.
+Similar to other services, NGINX and NGINX Plus use a text‑based configuration file with a precise format. By default the file is named **nginx.conf** and for NGINX Plus is placed in the `/etc/nginx` directory.
 
-For NGINX Open Source, the location depends on the package system used to install NGINX and the operating system. It is typically one of `**/usr/local/nginx/conf**`, `**/etc/nginx**`, or `**/usr/local/etc/nginx**`.
+For NGINX Open Source, the location depends on the package system used to install NGINX and the operating system. It is typically one of `/usr/local/nginx/conf`, `/etc/nginx`, or `/usr/local/etc/nginx`.
 
 ## Directives
 The configuration file consists of _directives_ and their parameters. Simple (single‑line) directives end with a semicolon ( `;` ). Other directives act as “containers” which group together related directives. Containers are enclosed in curly braces ( `{}` ) and are often referred to as _blocks_. Here are some examples of simple directives.

content/nginx/admin-guide/installing-nginx/installing-nginx-docker.md

@@ -35,7 +35,7 @@ The registry contains the following image types:
 - [NGINX Plus]({{< ref "/nginx/releases.md" >}}):</br>
   `https://private-registry.nginx.com/v2/nginx-plus/base`
 
-- [Unprivileged]({{< ref "/nginx/admin-guide/installing-nginx/installing-nginx-plus.md#nginx-plus-unprivileged-installation" >}}) installation of NGINX Plus:</br>
+- [Unprivileged]({{< ref "/nginx/admin-guide/installing-nginx/installing-nginx-plus.md#unpriv_install" >}}) installation of NGINX Plus:</br>
   `https://private-registry.nginx.com/v2/nginx-plus/rootless-base`
 
 - NGINX Plus bundled with [NGINX Agent](https://docs.nginx.com/nginx-agent/overview/):</br>

content/nginx/admin-guide/load-balancer/http-health-check.md

@@ -18,7 +18,7 @@ NGINX and F5 NGINX Plus can continually test your upstream servers, avoid the se
 <span id="prereq"></span>
 ## Prerequisites
 
-- For passive health checks, [NGINX Open Source](https://nginx.org/en/) or [NGINX Plus](https://www.nginx.com/products/nginx)
+- For passive health checks, [NGINX Open Source](https://nginx.org/en/) or [NGINX Plus](https://www.f5.com/products/nginx/nginx-plus)
 - For active health checks and the [live activity monitoring dashboard]({{< ref "nginx/admin-guide/monitoring/live-activity-monitoring.md" >}}), NGINX Plus
 - A load‑balanced group of [HTTP upstream servers]({{< ref "http-load-balancer.md" >}})
 

content/nginx/admin-guide/security-controls/configuring-oidc.md

@@ -119,7 +119,7 @@ The setup steps are similar for most identity providers, but some details may di
 
   Copy the **issuer** value. You will need it later when [configuring NGINX Plus as the Relying Party](#setup-oidc-provider2).
 
-5. Configure a logout URI - a URI that a user visits to initiate an RP‑initiated logout flow, for example, `https://demo.example.com/post_logout/`. (Optional, supported since [NGINX Plus R35](({{< ref "nginx/releases.md#r35" >}}))).
+5. Configure a logout URI - a URI that a user visits to initiate an RP‑initiated logout flow, for example, `https://demo.example.com/post_logout/`. (Optional, supported since [NGINX Plus R35]({{< ref "nginx/releases.md#r35" >}})).
 
 
 ## Configure the Relying Party (NGINX Plus) {#rp-setup}

content/nginx/deployment-guides/load-balance-third-party/apache-tomcat.md

@@ -440,7 +440,7 @@ HTTP/2 is fully supported in both <span style="white-space: nowrap;">NGINX Open
 
 - In <span style="white-space: nowrap;">NGINX Plus R8</span> and later, NGINX Plus supports HTTP/2 by default. (Support for SPDY is deprecated as of that release). Specifically:
 
-  In <span style="white-space: nowrap;">NGINX Plus R11</span> and later, the {{<nb>}}**nginx-plus**{{</nb>}} package continues to support HTTP/2 by default, but the {{<nb>}}**nginx-plus-extras**{{</nb>}} package available in previous releases is deprecated by [dynamic modules](https://www.nginx.com/products/nginx/dynamic-modules/).
+  In <span style="white-space: nowrap;">NGINX Plus R11</span> and later, the {{<nb>}}**nginx-plus**{{</nb>}} package continues to support HTTP/2 by default, but the {{<nb>}}**nginx-plus-extras**{{</nb>}} package available in previous releases is deprecated by [dynamic modules](https://www.f5.com/go/product/nginx-modules/).
 
   For <span style="white-space: nowrap;">NGINX Plus R8</span> through R10, the {{<nb>}}**nginx-plus**{{</nb>}} and {{<nb>}}**nginx-plus-extras**{{</nb>}} packages support HTTP/2 by default.
 
@@ -962,7 +962,7 @@ server {
 <span id="resources"></span>
 ## Resources
 
-- [NGINX Plus Overview](https://www.nginx.com/products/nginx)
+- [NGINX Plus Overview](https://www.f5.com/products/nginx/nginx-plus)
 - [NGINX Plus Admin Guide]({{< ref "/nginx/admin-guide/_index.md" >}})
 - [NGINX Wiki](https://www.nginx.com/resources/wiki/)