You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/DEPLOYMENT.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,6 +106,9 @@ or wants to have the Nuts node deployed separately, the Knooppunt can use that N
106
106
107
107
Use [`nuts.enabled`](./CONFIGURATION.md) to configure the embedded or existing Nuts node.
108
108
109
+
Note that you MUST configure the `url` (or `NUTS_URL`) property in the Nuts configuration to point to the **publicly accessible** base URL of the Knooppunt (the URL under which other Nuts nodes and clients can reach it). This is the URL the Nuts node advertises externally.
110
+
The Knooppunt runs the embedded Nuts node on `/nuts`, so if the Knooppunt is publicly reachable at `https://knooppunt.example.com/`, the Nuts node URL must be `https://knooppunt.example.com/nuts` (not an internal-only address such as `http://knooppunt:8080/nuts`).
111
+
109
112
### Tracing
110
113
111
114
The Knooppunt supports distributed tracing using OpenTelemetry. Traces can be sent to any OTLP-compatible collector (e.g. Jaeger, Grafana Tempo, or a vendor's existing observability platform).
0 commit comments