这是indexloc提供的服务，不要输入任何密码
Skip to content

Use the verb set up instead of the noun setup #192

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Dec 11, 2021
Merged

Use the verb set up instead of the noun setup #192

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/docs/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ No. [Remote Caching](./features/remote-caching) is optional. However, you'll fin

No. Turborepo does not store source code. Without Remote Caching, no code ever leaves your machine—it will only cache artifacts to local disk.

With Turborepo's Remote Caching, you are responsible for configuring cache behavior and should only setup Turborepo to cache compiled artifacts. Please be aware that Turborepo treats all logs as artifacts and so these _will_ be stored along with other cache artifacts. There is also a retention period of 14 days. In the future, this retention period will be configurable on a per-task basis.
With Turborepo's Remote Caching, you are responsible for configuring cache behavior and should only set up Turborepo to cache compiled artifacts. Please be aware that Turborepo treats all logs as artifacts and so these _will_ be stored along with other cache artifacts. There is also a retention period of 14 days. In the future, this retention period will be configurable on a per-task basis.

## Is Turborepo's Remote Caching secure?

Expand Down
2 changes: 1 addition & 1 deletion docs/pages/docs/features/remote-caching.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Then run the same build again. If things are working properly, `turbo` should no

### Remote Caching on Vercel Builds

If you are building and hosting your apps on Vercel, then Remote Caching will be automatically setup for you on your behalf once you use `turbo`. You just need to update your build settings to build with `turbo`.
If you are building and hosting your apps on Vercel, then Remote Caching will be automatically set up for you on your behalf once you use `turbo`. You just need to update your build settings to build with `turbo`.

Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/git/monorepos#turborepo?utm_source=turborepo.org&utm_medium=referral&utm_campaign=docs-link) for instructions.

Expand Down
2 changes: 1 addition & 1 deletion docs/pages/docs/upgrading-to-v1.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ If you were using Remote Caching for local development, upgrading will take a mi
npx vercel login
```

Now we can setup Remote Caching through Vercel by running:
Now we can set up Remote Caching through Vercel by running:

```sh
npx turbo link
Expand Down