Remote Cache server for Nx
Find a file
2025-05-12 07:22:48 +02:00
src improve configuration & documentation 2025-05-12 07:22:48 +02:00
.gitignore initial implementation of the Nx remote cache API 2025-05-11 08:15:46 +02:00
Cargo.lock initial implementation of the Nx remote cache API 2025-05-11 08:15:46 +02:00
Cargo.toml initial implementation of the Nx remote cache API 2025-05-11 08:15:46 +02:00
README.md improve configuration & documentation 2025-05-12 07:22:48 +02:00

enex-rcache - remote build cache implementation for Nx

This is an implementation of the Nx remote cache OpenAPI specification.

Configuration

enex-rcache takes its configuration from enviroment variables. Currently the following are supported:

  • ENEX_CACHE_DIR (required) - The directory in which to store cache records

  • ENEX_READ_TOKENS - Comma-separated list of tokens able to read from the cache, but not write to it.

    Note: If this list is empty, this cache does not have read-only users (i.e. all users must have read-write tokens).

  • ENEX_READ_WRITE_TOKENS (required) - Comma-separated list of tokens to write to the cache. Writing implies being able to read.

  • ENEX_BIND_ADDRESSES - comma-separated list of IP addresses to bind the service to. If empty the service will bind to all available interfaces.

enex-rcache will try to read a .env file at startup in order to set the environment. Existing enviroment entries will take precedence over the contents of the .env file (so you can have a standard config in a file and override it from the environment, e.g. in containerized deployments).