How to add a new registry to your workspace
Working with registries
Bytesafe registries are very lightweight and besides being containers for your packages dependencies, each registry is also its own entity and adhere to its own set of rules, as defined by you.
Users can create multiple registries, each with their own set of upstreams (linked private or public registries), organizing the flow of packages between different teams and the outside world.
Registries can be renamed, easily cloned and customized according to a users needs.
In addition to direct registry actions, Upstreams and Plugins & Policies are additional core features on top of each registry that define the flow of packages and the rules and constraints.
Upstreams are linked registries that are used both as a destination and source for packages in your private registries.
Upstreams can be:
- Public npm registry (registry.npmjs.org)
- Maven Central Repository (repo1.maven.org/maven2/)
- NuGet Gallery (nuget.org)
- Other Bytesafe registry
- Git repository
- URL to any npm, NuGet or Maven compatible registry
Package versions can be downloaded (“pulled”) from an upstream to a registry (either manually or when running npm install). Packages can also be published (“pushed”) from a Bytesafe registry up to an upstream.
A registry without upstreams will not be able to fetch packages from any outside source and packages from the registry can not be pushed from the registry to any other source either.
Upstream configurations enable custom workflows and secure management of packages. Easily configure a proxy to be used in between your project and the public npm registry.
For more information on how to configure upstreams as well as examples of upstream configurations for different use-cases, see the documentation section on Upstreams.
Plugins & Policies
Policies are rules that are executed before any registry action is applied. Example actions include Freeze that prevents any changes to the contents of a registry.
Plugins and policies are configured inside Bytesafe, in the Plugins tab for a registry. Bytesafe offers a number of built-in plugins and policies for use, but will also support custom and 3rd party integrations in the future.
The following pages will cover the common registry actions that users need to know to work with Bytesafe registries.
How to clone an existing registry
Overview of key metrics for your workspace and registries
How to delete an existing registry
How to delete an existing package from a registry
How to install and publish packages
Prevent internal packages from being fetched from external upstreams
How to access package information and pull different versions of a packages from upstreams
Analysis and display of license information
How to push or promote a package version to upstream or registry
How to use one of your registries as your default npm registry
How to manually upload a package version
Create reproducible and deterministic installs and builds for your whole team