How upstreams work
What happens when you pull a package with / without configured upstreams
Upstreams are linked registries that are used both as a source and destination for packages in your private registries. As such upstreams are used when the Bytesafe registry is unable to fulfill a request for a specific package version or to push package versions from the registry to other destination registries.
Upstreams empower your private registry to be able to store both private and public packages together and enable secure management of your package dependencies.
In Bytesafe upstreams can be any of the following:
A registry can also be configured without an upstream, removing the connection to other registries.
Example: Use case where Bytesafe registry is used as a proxy registry and the public npm registry is configured as an upstream.
graph TD
A(fab:fa-npm registry.npmjs.org) --- | pull / push | B{Bytesafe registry} --- | install / publish | C[fa:fa-user Project workspace]
What happens when you pull a package with / without configured upstreams
Adding and configuring upstreams for a registry
Connecting private and public Git repositories to Bytesafe