From e6dc37a9d8853ea5aee24c8adf041113c862c529 Mon Sep 17 00:00:00 2001 From: Anthony Shew Date: Thu, 13 Jul 2023 11:18:28 -0700 Subject: [PATCH 1/3] Fix link. --- docs/pages/repo/docs/core-concepts/remote-caching.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/pages/repo/docs/core-concepts/remote-caching.mdx b/docs/pages/repo/docs/core-concepts/remote-caching.mdx index 6f7c5421230e5..c342752813604 100644 --- a/docs/pages/repo/docs/core-concepts/remote-caching.mdx +++ b/docs/pages/repo/docs/core-concepts/remote-caching.mdx @@ -11,7 +11,6 @@ import { Tabs, Tab } from "../../../../components/Tabs"; Turborepo's [task cache](/repo/docs/core-concepts/caching) can save a lot of time by never doing the same work twice. But there's an issue - the **cache is local to your machine**. When you're working with a CI, this can result in a lot of duplicated work: - ![](/images/docs/local-caching.png) Since Turborepo only caches to the local filesystem by default, the same task (`turbo run build`) must be **re-executed on each machine** (by you, by your teammates, by your CI, by your PaaS, etc.) even when all of the task inputs are identical — which **wastes time and resources**. @@ -79,7 +78,7 @@ Then run the same build again. If things are working properly, `turbo` should no If you are building and hosting your apps on Vercel, Remote Caching will be automatically set up on your behalf once you use `turbo`. You need to update your [build settings](https://vercel.com/docs/concepts/deployments/configure-a-build) to build with `turbo`. -Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/git/monorepos#turborepo?utm_source=turbo.build&utm_medium=referral&utm_campaign=docs-link) for instructions. +Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/monorepos/turborepo?utm_source=turbo.build&utm_medium=referral&utm_campaign=docs-link) for instructions. ### Artifact Integrity and Authenticity Verification From 559bef97dcb8628e8eb51736a82fe9b4ef9cd937 Mon Sep 17 00:00:00 2001 From: Anthony Shew Date: Thu, 13 Jul 2023 11:19:58 -0700 Subject: [PATCH 2/3] Phrasing. --- docs/pages/repo/docs/core-concepts/remote-caching.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/repo/docs/core-concepts/remote-caching.mdx b/docs/pages/repo/docs/core-concepts/remote-caching.mdx index c342752813604..f766e1efb8eec 100644 --- a/docs/pages/repo/docs/core-concepts/remote-caching.mdx +++ b/docs/pages/repo/docs/core-concepts/remote-caching.mdx @@ -78,7 +78,7 @@ Then run the same build again. If things are working properly, `turbo` should no If you are building and hosting your apps on Vercel, Remote Caching will be automatically set up on your behalf once you use `turbo`. You need to update your [build settings](https://vercel.com/docs/concepts/deployments/configure-a-build) to build with `turbo`. -Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/monorepos/turborepo?utm_source=turbo.build&utm_medium=referral&utm_campaign=docs-link) for instructions. +Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/monorepos/turborepo?utm_source=turbo.build&utm_medium=referral&utm_campaign=docs-link) for more information. ### Artifact Integrity and Authenticity Verification From d2bf7831ab9f90dad77692ad544177e803a3e855 Mon Sep 17 00:00:00 2001 From: Anthony Shew Date: Thu, 13 Jul 2023 11:28:10 -0700 Subject: [PATCH 3/3] This one's better. --- docs/pages/repo/docs/core-concepts/remote-caching.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/repo/docs/core-concepts/remote-caching.mdx b/docs/pages/repo/docs/core-concepts/remote-caching.mdx index f766e1efb8eec..f422169384671 100644 --- a/docs/pages/repo/docs/core-concepts/remote-caching.mdx +++ b/docs/pages/repo/docs/core-concepts/remote-caching.mdx @@ -78,7 +78,7 @@ Then run the same build again. If things are working properly, `turbo` should no If you are building and hosting your apps on Vercel, Remote Caching will be automatically set up on your behalf once you use `turbo`. You need to update your [build settings](https://vercel.com/docs/concepts/deployments/configure-a-build) to build with `turbo`. -Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/monorepos/turborepo?utm_source=turbo.build&utm_medium=referral&utm_campaign=docs-link) for more information. +Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/monorepos/remote-caching?utm_source=turbo.build&utm_medium=referral&utm_campaign=docs-link) for more information. ### Artifact Integrity and Authenticity Verification