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
{{ message }}
Repository navigation
Commit 29b5c66
Browse filesBrowse the repository at this point in the historyBrowse files
deepshekhardas
committed
feat(webapp): add RUNTIME_API_ORIGIN to decouple runner traffic from external origin
Add `RUNTIME_API_ORIGIN` env var to route managed runner traffic through an in-cluster URL, bypassing tracing gateways that rewrite the W3C `traceparent` header and break parent→child run links.
Copy file name to clipboardExpand all lines: docs/self-hosting/env/webapp.mdx
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@ mode: "wide"
19
19
|`LOGIN_ORIGIN`| Yes |http://localhost:3030| Login origin URL. Most likely the same as `APP_ORIGIN`. |
20
20
|`API_ORIGIN`| No |`APP_ORIGIN`| API origin URL. |
21
21
|`STREAM_ORIGIN`| No |`APP_ORIGIN`| Realtime stream origin URL. |
22
+
|`RUNTIME_API_ORIGIN`| No | — | In-cluster origin used by managed (deployed) runners for `TRIGGER_API_URL`/`TRIGGER_STREAM_URL`. Set this to keep runner-to-webapp traffic on an internal hop that bypasses tracing-enabled gateways (which rewrite the W3C `traceparent` header and break the run-detail tree). Leave unset to keep using `API_ORIGIN`/`STREAM_ORIGIN`. |
22
23
|`ELECTRIC_ORIGIN`| No |http://localhost:3060| Electric origin URL. |
0 commit comments