@@ -19,7 +19,7 @@ the following:
1919
2020## Gitlab Version Compatibility
2121
22- - If ` legacy_mode: false ` : Gitlab 11.2+
22+ - If ` legacy_mode: false ` or undefined (default mode) : Gitlab 11.2+
2323- If ` legacy_mode: true ` : Gitlab 9.0+
2424
2525## Use it
@@ -89,35 +89,35 @@ and publish packages:
8989yarn publish --registry http://localhost:4873
9090```
9191
92- > ** NOTE** : In order to publish packages, you need to create or be part of
93- a GitLab group (as owner) which has the same name as your package name. You
94- also need a fresh login, so that Verdaccio recognizes your owned groups.
95- 9692## Access Levels
9793
9894Access and publish access rights depend on the mode used.
9995
96+ ### Normal Mode
97+ 10098In the default mode, packages are available:
10199
102100- * access* is allowed depending on verdaccio ` package ` configuration
103101 directives (unauthenticated / authenticated)
104102- * publish* is allowed if the package name matches the logged in user
105103 id, or if the package name / scope of the package matches one of the
106- user groups and the user has ` $ auth.gitlab.publish` access rights on
104+ user groups and the user has ` auth.gitlab.publish ` access rights on
107105 the group
108106
109107For instance, assuming the following configuration:
110108
111109- ` auth.gitlab.publish ` = ` $maintainer `
112- - the gitlab user ` sample_user ` had access to group ` group1 ` as
110+ - the gitlab user ` sample_user ` has access to group ` group1 ` as
113111 ` $maintainer ` and ` group2 ` as ` $reporter `
114112- then this user could publish any of the npm packages:
115113 - ` sample_user `
116114 - any package under ` group1/** `
117115 - error if the user tries to publish any package under ` group2/** `
118116
117+ ### Legacy Mode
118+ 119119If using the legacy mode, the system behaves as in normal mode with
120- fixed ` $ auth.gitlab.publish` = ` $owner `
120+ fixed configuration ` auth.gitlab.publish ` = ` $owner `
121121
122122## Configuration Options
123123
0 commit comments