Repository navigation
Replies: 1 comment 1 reply
|
A data point from a real setup: I tested #34302 end to end with Entra ID against the self-hosted relay, covering the web app, the CLI device flow and Android. The details are in the PR comments. On whether part of it could land on its own: for my use case the essential pieces are the Node host for the relay, OIDC sign-in with the ID token, and relay channels ( |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
T3 Connect only works through T3's hosted relay, or through a copy of it deployed on Cloudflare with Clerk. You cannot keep the whole connection path on one server you control, signed in with the identity provider you already run. A machine with no public address also needs a Cloudflare-managed tunnel to be reachable.
In August, #6033 proposed a self-hosted relay, and the answer was that deploying the relay to a VPS is "not something we wanna take on today". I needed it anyway, so I built it in my fork and now run it on my own server. Before anyone spends review time on it, I'd like to know whether that is still the answer, and whether part of it could land on its own.
What I built
Branch: TuroYT/t3code
t3/self-hosted-connect-service, opened as #34302infra/relay/selfhostholds a Docker Compose setup with Caddy and an operator guide. The hosted Worker is meant to behave exactly as before./.well-known/t3-relay. Web, desktop, mobile and the CLI sign in with the authorization code flow and PKCE.RELAY_CHANNELS=true, a machine with no public address keeps one outbound WebSocket open to the relay, and the relay serves it under<relay>/env/<key>/. Responses carried this way cannot act on the relay's own origin: their headers are allowlisted, cookies are dropped, and each response is sandboxed with CSP. A machine that has its own HTTPS address can publish that address instead.Not covered: managed tunnels, push notifications (they need the app publisher's credentials), webhooks held while an environment is offline, and running more than one relay replica.
Questions
All reactions