docs: document reverse proxy path prefixes

2026-07-12 23:28:20 +02:00
parent ceeb0d413d
commit a493949c2a
8 changed files with 170 additions and 4 deletions
@@ -394,6 +394,12 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
                UI should come from the selected PI WEB instance; on remote machines, the gateway copy is hidden unless
                the remote machine exposes its own copy.
              </p>
+              <p>
+                Current PI WEB manifests publish module references relative to the fetched manifest, so local and
+                federated plugin modules follow root or nested reverse-proxy deployments without a prefix-specific
+                build. The browser and federated gateway also accept leading-root module references emitted by existing
+                PI WEB releases and keep them inside the current application base.
+              </p>
              <p>
                For portable plugin assets, prefer URLs relative to the plugin module, such as
                <code>new URL("./asset.json", import.meta.url)</code>. If a remote plugin constructs absolute asset URLs,