Configure official private mirrors

Ravenstash supports one curated public registry for each current ecosystem:

Ecosystem	Official mirror
PyPI	PyPI
npm	npmjs.org
Maven	Maven Central

Configure during repository creation

When creating a repository, choose Official upstreams to connect the matching source to every selected ecosystem. Review the minimum package age for each mirror before saving the repository.

Configure an existing ecosystem

Open the package repository.
Open the Upstreams tab.
Select PyPI, npm, or Maven.
Enable its official upstream.
Review the connection’s minimum and optional maximum package age, or allow new releases immediately.
Save the change.

Developers can then install private packages and approved public dependencies through the same authenticated rvs target.

Remove a mirror

Remove the mirror from the selected ecosystem’s settings. Private packages remain available, while public dependencies from that source are no longer available through the repository.

Removing a connection does not turn the repository public and does not remove another ecosystem’s upstream.

When you remove a mirror that package resolution rules select, those rules lose it and keep their other sources; the page says how many rules are affected before you save. See Remove an upstream that a rule selects.

Control which source supplies a package

When a repository has several upstreams, the first source that has a package supplies all of its versions. See How upstream package resolution works. To keep the names you own away from a public registry, or to change the behavior for specific packages, add package resolution rules on the repository’s Rules tab.

Connect another package source

Official sources are managed by Ravenstash. To connect another public or authenticated package repository, create a custom package source.