Skip to content

Commit 506382f

Browse files
t3dotggclaude
andcommitted
docs: ship production T3 Connect public config in .env.example
The Clerk publishable key, JWT template, CLI OAuth client ID, and relay URL are public identifiers already baked into every release artifact. Filling in the real values makes 'cp .env.example .env' the entire setup step for cloud-enabled source builds, while a fresh clone still defaults to cloud-off. Co-Authored-By: Claude Fable 5 <[email protected]>
1 parent cf5c994 commit 506382f

2 files changed

Lines changed: 22 additions & 11 deletions

File tree

‎.env.example‎

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
# Optional: T3 Connect source builds
2-
# Leave these unset to disable optional T3 Connect features in local source builds.
3-
# Release builds inject their public values at build time. Do not add server-side
4-
# secrets to this file.
2+
# `cp .env.example .env` enables T3 Connect against the production deployment.
3+
# These are the same public identifiers baked into official release builds, not
4+
# secrets. Remove or comment them out to build with cloud features disabled.
5+
# Do not add server-side secrets to this file.
56

6-
# Get these from the Clerk Dashboard under API keys, JWT templates, and OAuth applications.
7-
# T3CODE_CLERK_PUBLISHABLE_KEY=pk_test_...
8-
# T3CODE_CLERK_JWT_TEMPLATE=t3-relay
9-
# T3CODE_CLERK_CLI_OAUTH_CLIENT_ID=oauthapp_...
7+
# Production Clerk instance. To use your own, get these from the Clerk Dashboard
8+
# under API keys, JWT templates, and OAuth applications.
9+
T3CODE_CLERK_PUBLISHABLE_KEY=pk_live_Y2xlcmsudDMuY29kZXMk
10+
T3CODE_CLERK_JWT_TEMPLATE=t3-relay
11+
T3CODE_CLERK_CLI_OAUTH_CLIENT_ID=hzxSgY2cH10sDU2r
1012

1113
# Optional: signed macOS passkey builds. The RP domain defaults to the Frontend API
1214
# hostname encoded in T3CODE_CLERK_PUBLISHABLE_KEY. Set the override only when Clerk
@@ -15,8 +17,9 @@
1517
# T3CODE_MACOS_PROVISIONING_PROFILE=/absolute/path/to/t3code.provisionprofile
1618
# T3CODE_CLERK_PASSKEY_RP_DOMAINS=example.clerk.accounts.dev,clerk.example.com
1719

18-
# Get this from your relay deployment. `infra/relay` deploys update it automatically.
19-
# T3CODE_RELAY_URL=https://relay.example.com
20+
# Production relay. For a self-hosted relay, `infra/relay` deploys update it
21+
# automatically.
22+
T3CODE_RELAY_URL=https://relay.t3.codes
2023

2124
# Optional: hosted app origin used by the CLI's out-of-band OAuth flow.
2225
# Defaults to https://app.t3.codes; override to test against a staging deployment.

‎docs/internals/t3-connect.md‎

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,16 @@ For the wider system diagram, see
1414

1515
## Application Keys
1616

17-
T3 Connect is disabled in a fresh clone. To enable it for source builds, add a repository-root `.env`
18-
or `.env.local` file:
17+
T3 Connect is disabled in a fresh clone. To enable it for source builds against the production
18+
deployment, copy the repository-root example file:
19+
20+
```sh
21+
cp .env.example .env
22+
```
23+
24+
`.env.example` carries the production public identifiers (the same values baked into official
25+
release builds). To target a different Clerk application or relay, set the values yourself in a
26+
repository-root `.env` or `.env.local` file:
1927

2028
```dotenv
2129
T3CODE_CLERK_PUBLISHABLE_KEY=<publishable key>

0 commit comments

Comments
 (0)