Client configuration

The URL, token, and team that turbo sends to this server.

Value	Environment variable	`turbo.json` key	Meaning
URL	`TURBO_API`	`remoteCache.apiUrl`	The server’s origin, such as `https://cache.example.com`, without a trailing slash or `/v8`.
Token	`TURBO_TOKEN`	None	The server’s bearer token.
Team slug	`TURBO_TEAM`	`remoteCache.teamSlug`	The artifact namespace shared by participating clients.
Team ID	`TURBO_TEAMID`	`remoteCache.teamId`	An alternative to a slug. `turbo` sends IDs that start with `team_`.
Signing key	`TURBO_REMOTE_CACHE_SIGNATURE_KEY`	None	The shared key used when `remoteCache.signature` is `true`.

turbo reads these values from the following sources. An earlier source wins over a later one:

Environment-only configuration

When no project configuration is committed, all three connection values are needed:

export TURBO_API='https://cache.example.com'
export TURBO_TOKEN='<your token>'
export TURBO_TEAM='my-team'

.turbo/config.json stores settings for one checkout:

{
    "apiUrl": "https://cache.example.com",
    "teamSlug": "my-team",
    "token": "<your token>"
}

The file holds the token, so keep .turbo in your .gitignore.

Connect turbo covers the recommended setup and how to check it.