You need to enable JavaScript to run this app.
Container Registry

Container Registry

Copy page
Download PDF
Creating a repository
Creating an NPM repository
Copy page
Download PDF
Creating an NPM repository
A repository serves as the primary level for package management within R&D organizations, designed to manage various types of repositories and the resources housed within them. Different repositories can logically isolate data, provide independent repository access URLs, and allow for the configuration of distinct policies. Before uploading or downloading packages in an artifact repository instance, it is essential to create an artifact repository first. This document guides you through the process of creating an artifact repository.​
Prerequisites​
  • Have registered a Volcano Engine root user and activated the artifact repository Service.​
  • A repository instance has been created. For details, refer to Creating basic edition instances.​
Create a Hosted-type repository​
  1. Log in to the Artifact repository console.​
  1. In the left navigation bar, select Instances. Then, in the Instances area, click on the instance name to access the artifact repository instance configuration interface.​
  1. At the top of the left navigation bar, select the NPM package format, and then in the menu bar, choose Repository Management and click on New Repository to enter the repository configuration page.​
  1. Configure a Hosted-type artifact repository.​
  • ​
    Parameter​
    Description​
    Repository Type​
    Configure the type of the artifact repository. Only the Hosted type is supported.​
    Repository Name​
    Configure the name of the artifact repository to distinguish different repositories.​
    Repository names are unique within an instance, but not globally, which means that different instances can have repositories with the same name.​
    Package Format​
    Fixed as NPM in this example and can not be modified.​
    Permission Scope​
    Configure the permission scope of the artifact repository, including:​
    • Public: The repository is open to the public, allowing anonymous downloads of packages.​
    • Team-internal: The repository is only accessible within the team.​
    Package Update Strategy​
    Configure the package update strategy of the artifact repository, including:​
    • Prohibit Overwriting: Indicates that only one package release is allowed.​
    • Allow Overwriting: Indicates that multiple package releases are allowed, with newly released packages overwriting older ones.​
    • Read-only: Indicates that package releases are prohibited, and only downloads from the repository are allowed.​
    Description​
    Describe the artifact repository. Detailed information about the repository, such as the project to which it belongs, can be included here.​
    ​
  1. Click Confirm to complete the creation of the artifact repository.​
​
Last updated: 2025.10.24 11:20:40