Proxy Caching

Proxy caching gives developers a RepoFlow endpoint for upstream packages while reducing repeated requests to the original registry.

At a glance

• A remote repository proxies one upstream package registry.
• With remote cache enabled, RepoFlow stores fetched artifacts for later requests.
• Separate revalidation times control package files and frequently changing metadata.
• A virtual repository can expose local and remote repositories through one client endpoint.

Use proxy caching

1. Create a repository and choose Remote.
2. Select the package type and enter the upstream registry URL.
3. Add upstream credentials when the registry is private.
4. Enable Remote Cache and choose revalidation times, or leave them empty for no expiration.
5. Open Repository Setup and configure your package client with the RepoFlow endpoint.
6. Install packages normally. RepoFlow fetches a missing artifact from upstream and can serve later requests from its cache.

Metadata and package files change at different rates. Use a shorter metadata revalidation period when newly published versions must appear quickly, and a longer file period for immutable artifacts.

Add a virtual repository

Use a virtual repository when developers should not need separate URLs for internal and upstream packages:

1. Create a Virtual repository for the same package type.
2. Add local and remote child repositories in the order RepoFlow should check them.
3. Configure package clients with the virtual repository endpoint.

Resolution order matters when the same package exists in more than one child repository. Put the repository you trust or prefer first.

Inspect and manage cached content

Cached packages appear in RepoFlow so you can inspect their versions, files, and scan results. Repository administrators can also:

• List repository files to inspect cached paths.
• Delete repository content to clear remote cache content.
• Update repository settings to change cache and revalidation behavior.

For the difference between local, remote, and virtual repositories, see Repositories.

Self-hosted deployments can disable caching platform-wide with IS_REMOTE_CACHE_ENABLED. See Server Environment Variables.