repowiseducktors/turborepo-remote-cache

ducktors / turborepo-remote-cache Architecture and code health

Open source implementation of the Turborepo custom remote cache server.

TypeScript★ 1,492
Use in your agentAsk this codebase

github.com/ducktors/turborepo-remote-cacheIndexed at 9efa1c6Up to date with upstream

What is turborepo-remote-cache?

turborepo-remote-cache is an open-source implementation of the Turborepo custom remote cache server. It is meant for self-hosted deployments where Vercel's official cache server is not a viable option. It runs as a server that Turborepo calls to store and serve cache data through a range of supported storage providers, and it is written in TypeScript.

Written by a model from the README and the source

105 files and 167 symbols in 5 modules, led by TypeScript (54 files) and JavaScript (2).

Start reading

Code health

8.4out of 10Good

Hotspots average 7.5, the place fixes pay off most.

Full health report

Use ducktors/turborepo-remote-cache in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

  1. 1.In Claude, open Customize → Connectors, click +, then Add custom connector. On a Team or Enterprise plan an owner adds it first under Organization settings → Connectors.
  2. 2.Paste the server URL below as the Remote MCP server URL, then click Add.
  3. 3.Click Connect. A Repowise sign-in window opens. Approve access.
  4. 4.Repowise's tools are now available in your Claude chats.

Connect with one click. Sign in with Repowise (OAuth), no API key to copy. Works in Claude on the web, desktop, and mobile.

Docs
bash
https://api.repowise.dev/mcp/ducktors/turborepo-remote-cache
Editors need an API key: sign in to create one.Sign in to connect

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is turborepo-remote-cache put together?")
  • get_why("why is turborepo-remote-cache structured this way?")

Explore turborepo-remote-cache

Key features of turborepo-remote-cache

  • Provides an open-source implementation of the Turborepo custom remote cache server.
  • Serves as an alternative to Vercel's official cache server for self-hosted deployments.
  • Supports a range of storage providers, listed in the Supported Storage Providers documentation.
  • Offers deploy buttons for one-click deployments of the server where possible.
  • Creates releases automatically from Conventional Commits messages using Semantic Release.

How ducktors/turborepo-remote-cache works

The project has three entry points, src/index.ts, src/app.ts and src/cli.ts, which start the server and its command line interface. The server is built on Fastify, as shown by the fastify dependency, and @fastify/jwt handles JWT authentication. Storage backends are connected through the storage plugin in src/plugins/remote-cache/storage, whose index file src/plugins/remote-cache/storage/index.ts is listed among the project's hotspot files. The storage backends use the AWS S3, Azure Blob Storage and Google Cloud Storage client libraries. The src directory holds the server code, and the test directory holds the test suite, including test/jwt-auth.ts and test/azure-blob-storage.ts. The package.json file at the root defines the npm package.

The codebase has 105 files and 167 symbols in 5 modules, led by TypeScript, JavaScript and Dockerfile. Code health is 8.4 out of 10, rated good.

ducktors/turborepo-remote-cache FAQ

What is turborepo-remote-cache?

turborepo-remote-cache is an open-source implementation of the Turborepo custom remote cache server. It is intended for self-hosted deployments where Vercel's official cache server is not a viable option.

How does turborepo-remote-cache work?

turborepo-remote-cache runs as a server that Turborepo calls to store and retrieve cache data. It connects to supported storage providers, and its storage plugin lives under src/plugins/remote-cache/storage.

What language is turborepo-remote-cache written in?

turborepo-remote-cache is written mainly in TypeScript. The repository also contains some JavaScript, a Dockerfile and a shell script.

How is the turborepo-remote-cache code organized?

Server code lives in the src directory and tests live in the test directory. The entry points are src/index.ts, src/app.ts and src/cli.ts.

Who is turborepo-remote-cache for?

turborepo-remote-cache is for self-hosted deployments of the Turborepo remote cache where Vercel's official cache server is not a viable option. It supports storage providers and deploy buttons for one-click deployments.

What license does turborepo-remote-cache use?

turborepo-remote-cache is licensed under MIT, the license identifier given for the project.

The summary, features and answers on this page are written by a model from the README and the source, and refreshed with each index.

About this page

Get a page like this for your own codebase

Repowise built this map of ducktors/turborepo-remote-cache from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Index your repo freeSee how Repowise worksFree for 2 public repos, with a page like this one.

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.