generated from qtrn-io/repo-template
feat: add the turbo-cache recipe (Turborepo remote cache) #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/6-turbo-cache-recipe"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #6
Change
New platform recipe
turbo-cache: the open-source serverducktors/turborepo-remote-cache(MIT), pinned to 3.0.3, with artifacts in an S3-compatible bucket.k8s/stacks/turbo-cache/base: Namespace, Deployment, Service, NetworkPolicy.tycho/recipes/k8s/turbo-cache/package.jsonand five variables in.tycho/repository.jsonsecrets.dist.yaml,README.mdandREADME.fr.mdThe cache is an internal service: it has no public route, and the NetworkPolicy lets only the namespace
forgejo-runnerreach it. The README says what a deployment with clients outside the cluster must add.Change to the
forgejo-runnerrecipe (1.0.0 → 1.1.0)The runner reads an optional Secret
forgejo-runner-job-env(dotenv file) and gives its variables to every job. This is how jobs receive the address and the credentials of the cache, without any setting on a repository or an organisation.base/configmap.yaml:runner.env_filebase/scaledjob.yaml: the Secret is mounted withoptional: truesecrets.dist.yaml: template of the SecretWithout the Secret, the rendered runner behaves as before: the runner ignores a missing file. The ScaledJob template changes, so a deployment that upgrades rolls its runner jobs.
Verified
bun run validatepasses; both bases render withkubectl kustomize.env_fileand the handling of a missing file were read in the source of the runner at v13.0.0.Not verified: the S3 storage mode, the recipe on a cluster, and a job actually receiving the variables.
Known
The
CIworkflow of this repository still fails on the secret scan (x64 binary on arm64 runners); the fix is onfix/ci-runner-architecture.🤖 Generated with Claude Code