Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 7 additions & 0 deletions .github/styles/config/vocabularies/TraceMachina/accept.txt
Original file line number Diff line number Diff line change
@@ -1,16 +1,23 @@
[Aa]gentic
Ansys
Anthropic
AMI
Astro
Bazel
Bazelisk
[Bb]oolean
Cloudflare
Colab
CPUs
ELB
FFI
FFIs
GPUs
Goma
[Hh]ermeticity
JDK
json
JSON
Kustomization
Kustomizations
LLD
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,11 @@ which both provide helpful reference for customers looking to deploy NativeLink
## Production CAS Overview
At NativeLink we offer CAS-as-a-Service running on all the major cloud providers (AWS, GCP, Azure, etc). This allows our customers to get started with NativeLink to improve build & test performance with minimal effort. Behind the scenes, each CAS service runs in a Kubernetes namespace with a dedicated ActionCache store and a shared CAS store. In this article, we take a deep dive into how we Configure the CAS service in our cloud. Even if you’re not using our hosted CAS service, the insights covered here will help you Configure your own CAS to achieve high performance and scalability.

To run NativeLink, you just pass the path to a single JSON Configuration file, such as:
To run NativeLink, you just pass the path to a single JSON5 Configuration file, such as:

/bin/NativeLink /etc/Config/cas.json
```bash
/bin/NativeLink /etc/Config/cas.json5
```

The entire JSON file we use for the cloud service is included at the end of this document.
NativeLink Servers
Expand Down
Loading
Loading