Skip to main content

Didabobo awọn akopọ

Verdaccio allows you protect publishing to your registry. To achieve that you will need to set up correctly configure your packages access.

Iṣeto akopọ

Let's see for instance the following set up. You have a set of dependencies that are prefixed with my-company-* and you need to protect them from anonymous or other non-authorized logged-in users.

'my-company-*':
access: admin teamA teamB teamC
publish: admin teamA
proxy: npmjs

Pẹlu iṣeto yii, lakotan a fayegba awọn ẹgbẹ admin ati teamA lati se atẹjade ati teamA teamB teamC wiwọle si awọn igbarale bẹ.

Lo apẹẹrẹ: teamD gbiyanju lati wọle si igbarale naa

So, if I am logged as teamD. I shouldn't be able to access all dependencies that match the my-company-* pattern.

npm whoami
teamD

I won't have access to such dependencies and they also won't be visible via the web interface for user teamD. If I try to access it, the following will happen:

npm install my-company-core
npm ERR! code E403
npm ERR! 403 Forbidden: webpack-1@latest

tabi pẹlu yarn

yarn add my-company-core
yarn add v0.24.6
info No lockfile found.
[1/4] 🔍 Resolving packages...
error An unexpected error occurred: "http://localhost:5555/webpack-1: unregistered users are not allowed to access package my-company-core".