Setting the file. One moment.
Subchapter 9.7
references/caching/remote-cache.mdMarkdown2 KBView on GitHub
Free, zero-config when deploying on Vercel. For local dev and other CI:
# Authenticate with Vercel
npx turbo login
# Link repo to your Vercel team
npx turbo linkThis creates .turbo/config.json with your team info (gitignored by default).
Set these environment variables:
TURBO_TOKEN=<your-token>
TURBO_TEAM=<your-team-slug>Get your token from Vercel dashboard → Settings → Tokens.
GitHub Actions example:
- name: Build
run: npx turbo build
env:
TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
TURBO_TEAM: ${{ vars.TURBO_TEAM }}{
"remoteCache": {
"enabled": true,
"signature": false
}
}Options:
enabled: toggle remote cache (default: true when authenticated)signature: require artifact signing (default: false)Verify cache artifacts haven’t been tampered with:
# Set a secret key (use same key across all environments)
export TURBO_REMOTE_CACHE_SIGNATURE_KEY="your-secret-key"Enable in config:
{
"remoteCache": {
"signature": true
}
}Signed artifacts can only be restored if the signature matches.
Community implementations for running your own cache server:
Configure with environment variables:
TURBO_API=https://your-cache-server.com
TURBO_TOKEN=your-auth-token
TURBO_TEAM=your-team# Disable remote cache for a run
turbo build --remote-cache-read-only # read but don't write
turbo build --no-cache # skip cache entirely
# Environment variable alternative
TURBO_REMOTE_ONLY=true # only use remote, skip local# Verbose output shows cache operations
turbo build --verbosity=2
# Check if remote cache is configured
turbo configLook for: