Self-Host the Remote Cache
The recommended way to enable the remote cache is to use Nx Replay and have Nx Cloud share the task cache across your organization. For those organizations that are unable to use Nx Cloud, Nx offers official plugins that are enabled by Nx Powerpack to self-host the remote cache in a fast and secure manner. Powerpack is available for Nx version 19.8 and higher. The recommended ways to host the remote cache are, in order of preference:
- Nx Replay: Cache is hosted on Nx Cloud servers or on-premise with an Nx Enterprise contract
- @nx/powerpack-s3-cache: Cache is self-hosted on an Amazon S3 bucket
- @nx/powerpack-gcs-cache: Cache is self-hosted on Google Cloud storage
- @nx/powerpack-azure-cache: Cache is self-hosted on Azure
- @nx/powerpack-shared-fs-cache: Cache is self-hosted on a shared file system location
The options range from fully opting in to Nx's management of the remote cache to fully managing the configuration and security of your own remote cache.
Setup
All the self-hosted cache storage plugins require an Nx Powerpack license to function. Activating Powerpack is a simple process.
Buy a Powerpack LicenseUnlock all the features of the Nx CLI
Then, choose the appropriate cache plugin for your situation.
Amazon S3 Bucket Remote Cache
Google Cloud Storage Remote Cache
Azure Remote Cache
Shared Network Drive Remote Cache
Switch to Nx Cloud
These custom remote cache storage solutions only provide the remote cache functionality of Nx Cloud. If you want to leverage distributed task execution, re-running flaky tasks or automatically splitting tasks, you'll need to connect to Nx Cloud and use Nx Cloud's remote cache solution instead.
Connect to Nx CloudEnable task distribution and Atomizer