-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix disabled caching in Turbo #208
Comments
@jamesfrye420 Wanna give this a shot? |
Only api or all workspaces? |
Yeah for all over, and the |
Do you want to do remote caching or just local caching? |
Nvm remote caching can be setup later, no need as of now |
I'm not entirely sure what would be the best. Last time we used NX cloud cache. So maybe this time too, we can go with cloud caching? |
Yea basically it is the same Do you wanna host the cache in vercel or self host it? |
@rajdip-b could you list out all the workspaces in the project?
am I missing out anyhing? |
Nah thats all! |
We need to host it? :) can you send me some refs? |
Is docs a part of workspaces? |
Umm you have 2 options, one is local cache which is specific to a local machine and stored and consumed by it Other is cloud cache which is updated each time a new build is done and is shared by all machines |
Uh, ig we should stick to local rn |
Description
Currently, whenever we try to run tests, the scripts re-compile the
build
phase andtest:unit
phase of API over and over again. We would like to use turbo remote caching to help speed things up.The text was updated successfully, but these errors were encountered: