You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a corporate environment administrators may want to restrict access to public packages by providing a whitelist of packages that developers may use.
I propose a feature by which server administrators can configure such a whitelist and all packages retrieved from the public registry will be filtered against said whitelist. I suggest the whitelist to be configured as a property in the server's config JSON, e. g.:
"publicPackagesWhitelist" : ["angular"]
The filter will be applied to bower search as well as bower install of course.
If the property is omitted in the config JSON, all packages from the public registry will be provided.
The text was updated successfully, but these errors were encountered:
In a corporate environment administrators may want to restrict access to public packages by providing a whitelist of packages that developers may use.
I propose a feature by which server administrators can configure such a whitelist and all packages retrieved from the public registry will be filtered against said whitelist. I suggest the whitelist to be configured as a property in the server's config JSON, e. g.:
"publicPackagesWhitelist" : ["angular"]
The filter will be applied to bower search as well as bower install of course.
If the property is omitted in the config JSON, all packages from the public registry will be provided.
The text was updated successfully, but these errors were encountered: