History

docs: ship production T3 Connect public config in .env.example (#5573)

Theo Browne committed 3 months ago

Commit 4a07c1c1 parent cf5c9942 files · +22 −11Browse files

Showing the changes to docs (1 of 2 files). Show all

Unified · Split

docs/internals/t3-connect.md+10−2
@@ -14,8 +14,16 @@ For the wider system diagram, see · 13 unmodified lines
14 14
15## Application Keys15## Application Keys
16 16
17T3 Connect is disabled in a fresh clone. To enable it for source builds, add a repository-root `.env`17T3 Connect is disabled in a fresh clone. To enable it for source builds against the production
18or `.env.local` file:18deployment, copy the repository-root example file:
19
20```sh
21cp .env.example .env
22```
23
24`.env.example` carries the production public identifiers (the same values baked into official
25release builds). To target a different Clerk application or relay, set the values yourself in a
26repository-root `.env` or `.env.local` file:
19 27
20```dotenv28```dotenv
21T3CODE_CLERK_PUBLISHABLE_KEY=<publishable key>29T3CODE_CLERK_PUBLISHABLE_KEY=<publishable key>

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t