You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came from Rushjs background and they have this feature where the cache is writable by CI systems but read-only for developers on their workstation. Quoting their docs:
In a typical setup, the CI system would be configured to write to cloud storage, and individual users are granted read-only access. For example, each time a PR is merged into the main branch, the CI system builds that baseline and uploads it to cloud storage. Even for a user who is doing git clone for the first time, their rush build will be very fast.
It’d be great if turborepo-remote-cache has a flag to allow some tokens to read from the cache but not write to it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, thanks for this project!
I came from Rushjs background and they have this feature where the cache is writable by CI systems but read-only for developers on their workstation. Quoting their docs:
It’d be great if
turborepo-remote-cache
has a flag to allow some tokens to read from the cache but not write to it.Beta Was this translation helpful? Give feedback.
All reactions