nsc cache turborepo setup - Namespace Documentation

Documentation Index

Fetch the complete documentation index at: /docs/llms.txt

Use this file to discover all available pages before exploring further.

Assistant

Responses are generated using AI and may contain mistakes.

Set up Turborepo remote caching and output the required environment variables.Namespace provides high-performance Turborepo remote caching, backed by storage running alongside your jobs. cache turborepo setup issues a short-lived cache token and prints the TURBO_* environment variables that turbo needs to talk to the Namespace cache.The command does not modify your repository or shell: it writes KEY=value lines to stdout, so you can export them locally or append them to a CI environment file.Learn more about Turborepo caching →

Usage

nsc cache turborepo setup --team <team> \
    [--mask-auto] \
    [--mask-buildkite] \
    [--mask-github-actions] \
    [--output <plain|json>] \
    [--read-only] \
    [--token <path>] \
    [--token_duration <duration>]

Example output

nsc cache turborepo setup --team main

Output

TURBO_API=https://turbo.cache.namespaceapi.com
TURBO_TEAM=main
TURBO_TOKEN=nsct_...

Example in a local shell

Export the generated configuration into your shell, then run turbo as usual:

export $(nsc cache turborepo setup --team main)
turbo build

Example in GitHub Actions

Append the generated configuration to $GITHUB_ENV so that subsequent steps pick it up:

nsc cache turborepo setup --team main --mask-github-actions >> "$GITHUB_ENV"

Example in Buildkite

export $(nsc cache turborepo setup --team main --mask-buildkite)
turbo build

Options

—team

The Turborepo team to use. Teams isolate caches from each other, so different projects can share a workspace without sharing cache entries.This flag is required. Use nsc cache turborepo list to see the teams that already have cached artifacts.

—read-only

Only read from the remote cache. Sets TURBO_CACHE=local:rw,remote:r in the generated configuration, so turbo still writes to the local cache but never uploads to the remote one.Use this for workloads that should benefit from the cache without being able to poison it, such as builds of untrusted pull requests. To enforce read-only access on the server side as well, run the command with a token that only carries the read action:

nsc token create \
  --name "turborepo-cache-read-only" \
  --grant '{"resource_type":"cache/turborepo","resource_id":"*","actions":["read"]}'

See Permissions for the full list of cache/turborepo actions.

—mask-buildkite

Mask the generated token in Buildkite, so it is redacted from job logs.Requires buildkite-agent on PATH; the command fails if it is not found.

—mask-github-actions

Mask the generated token in GitHub Actions, so it is redacted from workflow logs.

—mask-auto

Mask the generated token in a detected CI environment. Supported environments are GitHub Actions and Buildkite. Use this when the same script runs in more than one CI system.

—output, -o

Output format. One of plain or json. Default is plain.json emits the same values as an object, which is convenient when a wrapper script needs to parse them:

{
  "api": "https://turbo.cache.namespaceapi.com",
  "team": "main",
  "token": "nsct_..."
}

—token_duration

The minimum duration of the configured token. Default is 4h. Raise it for jobs that run longer than the default token lifetime.

—token

Use the bearer token stored at this location for authentication instead of the default.

Related Topics

nsc cache turborepo list - List teams with cached artifacts
nsc token create - Create scoped, revokable tokens
Turborepo caching - Turborepo caching overview and CI setup
Permissions - cache/turborepo resource types and actions

Last modified onAugust 31, 2026

Ctrl+I

Documentation Index

​ Usage

​ Example output

​ Example in a local shell

​ Example in GitHub Actions

​ Example in Buildkite

​ Options

​ —team

​ —read-only

​ —mask-buildkite

​ —mask-github-actions

​ —mask-auto

​ —output, -o

​ —token_duration

​ —token

​ Related Topics