Upstream proxying and caching allows you to upload and use the packages you own, while Cloudsmith fetches and caches other packages (such as dependencies).
This enables you to use Cloudsmith as a first-class cache and a central source of truth for packages, to protect you from outages of external services (which is especially important when running behind your firewall).
Note: All formats are on the roadmap for Configurable Proxy and Caching.
Click the green "Create Upstream" button, you will then be presented with the "Create Maven Upstream Source" form:
|Name||A descriptive name for this upstream source. A shortened version of this name will be used for tagging cached packages retrieved from this upstream.|
|Weighting||The weighting of the Upstream source. Upstream sources are selected for resolving requests by descending priority (higher to lower), followed by creation date.|
|Upstream URL||The URL for this upstream source. This must be a fully qualified URL including any path elements required to reach the root of the repository.|
|Operating Mode||By default, upstream sources proxy requests through to match assets that are not present in this repository. On supported formats, proxy/caching may be selected to store resolved assets in this repository for future requests.|
|Verify SSL Certificates||If enabled, SSL certificates are verified when requests are made to this upstream. We recommended leaving this enabled for all public sources to help mitigate Man-In-The-Middle (MITM) attacks.|
|Authentication Username and|
Authentication Password (optional)
|Optional credentials that can be provided if the upstream is not publicly accessible|
|Headers (optional)||Optional Key-Value headers that can be passed to upstreams with each request.|
Click the blue "Edit Upstream" button to edit an upstream source:
Click the orange "Disable Upstream" button to disable an upstream source:
Click the red "Disable Upstream" button to disable an upstream source:
Updated about a month ago