Multiple ecosystems in one repository

A package repository has one owner and one name. It can support any combination of PyPI, npm, and Maven.

For owner acme and repository packages, each enabled ecosystem has its own repository URL:

PyPI:  https://pypi.pkg.rvsta.sh/x/_wsabc123/_repo1234/simple/
npm:   https://npm.pkg.rvsta.sh/x/_wsabc123/_repo1234/
Maven: https://maven.pkg.rvsta.sh/x/_wsabc123/_repo1234/

Upload routes use the same path under *.push.rvsta.sh.

Shared by the repository	Separate for each ecosystem
Owner and name	Package-manager integration and URLs
Rename, delete, and restore actions	Packages, versions, files, and package details
Bulk age-setting convenience	Upstream connection and explicit minimum/maximum age bounds
Combined usage totals	Ecosystem usage and cached package activity

Select the PyPI, npm, or Maven tab before browsing packages or changing ecosystem settings.

Add or remove ecosystem support

• A repository must always have at least one enabled ecosystem.
• You can enable another supported ecosystem at any time.
• You can remove an ecosystem only when it contains no private packages and at least one other ecosystem remains enabled.
• Re-enabling an ecosystem restores its previous configuration. Review its upstream settings before use.
• Renaming changes the repository URLs for every enabled ecosystem.
• Deleting the repository disables every enabled ecosystem together.

Note

A remote cache & proxy is a special read-only repository for one ecosystem. It provides a private, authenticated, mirror-like endpoint for a curated public registry and can also supply packages to your private repositories.