Point CI Turborepo remote cache at hosted turbo-cache.app.ju.ma #294

New issue

Closed

opened 2026-06-05 14:59:14 +00:00 by steve · 0 comments

steve commented

2026-06-05 14:59:14 +00:00

Owner

Problem

CI jobs start a per-run turbo-cache-server sidecar (or a macOS host server) backed by R2 repository secrets. A hosted cache server now runs at https://turbo-cache.app.ju.ma with artifact signing enabled.

Goal

Point Forgejo/GitHub turbo-enabled workflows and local docker:ci-check --remote-cache at the hosted server using client credentials only.

Scope

Workflow env updates across Forgejo and GitHub turbo jobs
scripts/turbo-cache-config.mjs and docker:ci-check remote-cache helpers
turbo.json remote cache signature
.env.example and release-management / monorepo-scripts spec pages

Non-goals

Deleting legacy composite actions under .github/actions/turbo-remote-cache/
Migrating hosted-server infrastructure itself

Acceptance Criteria

Turbo-enabled CI jobs set TURBO_API=https://turbo-cache.app.ju.ma, TURBO_TEAM=lapis-notes, TURBO_TOKEN, and TURBO_REMOTE_CACHE_SIGNATURE_KEY without per-job cache sidecars.
turbo.json enables remote cache artifact signing.
Local docker:ci-check remote cache uses the same client env keys documented in .env.example.
Spec docs describe the hosted cache and required secrets.

Implementation Notes

Centralize the hosted URL in scripts/turbo-cache-config.mjs. Remove service-container and wait steps from workflows.

Suggested Files or Specs To Inspect

.forgejo/workflows/checks.yml
.forgejo/workflows/release-desktop.yml
scripts/turbo-cache-config.mjs
spec/src/80-maintenance/release-management.md

Validation Commands

node --test scripts/run-lapis-ci-turbo-cache.test.mjs scripts/run-lapis-ci-check.test.mjs
pnpm check:all

Follow-up to #274 — Wire Turborepo remote cache to Cloudflare R2 in CI

Follow-up Tasks

Implementation Summary

Pointed Forgejo/GitHub turbo CI jobs and docker:ci-check remote cache at https://turbo-cache.app.ju.ma with TURBO_TOKEN and TURBO_REMOTE_CACHE_SIGNATURE_KEY; removed per-job turbo-cache-server sidecars; enabled turbo.json remoteCache.signature. Validated turbo-cache script tests and pnpm spec:lint.

## Problem CI jobs start a per-run `turbo-cache-server` sidecar (or a macOS host server) backed by R2 repository secrets. A hosted cache server now runs at `https://turbo-cache.app.ju.ma` with artifact signing enabled. ## Goal Point Forgejo/GitHub turbo-enabled workflows and local `docker:ci-check --remote-cache` at the hosted server using client credentials only. ## Scope - Workflow env updates across Forgejo and GitHub turbo jobs - `scripts/turbo-cache-config.mjs` and docker:ci-check remote-cache helpers - `turbo.json` remote cache signature - `.env.example` and release-management / monorepo-scripts spec pages ## Non-goals - Deleting legacy composite actions under `.github/actions/turbo-remote-cache/` - Migrating hosted-server infrastructure itself ## Acceptance Criteria 1. Turbo-enabled CI jobs set `TURBO_API=https://turbo-cache.app.ju.ma`, `TURBO_TEAM=lapis-notes`, `TURBO_TOKEN`, and `TURBO_REMOTE_CACHE_SIGNATURE_KEY` without per-job cache sidecars. 2. `turbo.json` enables remote cache artifact signing. 3. Local `docker:ci-check` remote cache uses the same client env keys documented in `.env.example`. 4. Spec docs describe the hosted cache and required secrets. ## Implementation Notes Centralize the hosted URL in `scripts/turbo-cache-config.mjs`. Remove service-container and wait steps from workflows. ## Suggested Files or Specs To Inspect - `.forgejo/workflows/checks.yml` - `.forgejo/workflows/release-desktop.yml` - `scripts/turbo-cache-config.mjs` - `spec/src/80-maintenance/release-management.md` ## Validation Commands - `node --test scripts/run-lapis-ci-turbo-cache.test.mjs scripts/run-lapis-ci-check.test.mjs` - `pnpm check:all` ## Related Issues - Follow-up to #274 — [Wire Turborepo remote cache to Cloudflare R2 in CI](../closed/274-wire-turborepo-remote-cache-to-cloudflare-r2-in-ci.md) ## Follow-up Tasks ## Implementation Summary Pointed Forgejo/GitHub turbo CI jobs and docker:ci-check remote cache at https://turbo-cache.app.ju.ma with TURBO_TOKEN and TURBO_REMOTE_CACHE_SIGNATURE_KEY; removed per-job turbo-cache-server sidecars; enabled turbo.json remoteCache.signature. Validated turbo-cache script tests and pnpm spec:lint.

steve

2026-06-05 14:59:14 +00:00