Q2 Artifactory for Portal Framework
Status
Release Available | Status | Framework Name |
|---|---|---|
| 4.2 | Current | Both MUI and Mint |
General
The .npmrc file is added to update the portal project registry endpoint. This points to an internal Q2 location for the npm installation of node modules.
Artifactory supports the notion of “virtual” repositories. Artifactory allows you to define a virtual repository which is a collection of local, remote, and other virtual repositories accessed through a single logical URL.
Q2 has configured a virtual repository virt-npm to point to two npm repositories.
npm-remote, which points to https://registry.npmjs.org
npm-local, which is a repository within Artifactory where Q2 packages are stored.
Simply, set your .npmrc file to use the virt-npm repository within Artifactory. Artifactory will then proxy the request to the repository that physically has the package requested.
Example
Examples of .npmrc files set up to use the virt-npm repo are :
https://bitbucket.q2ebanking.com/projects/QFE/repos/ngam/browse/packages/q2-uux/.npmrc
One liner
registry = https://aus-bin-prd-00.q2dc.local/artifactory/api/npm/virt-npm
https://gitlab.com/q2e/development/multitenant/qcon/apps/dcm-admin/-/blob/develop/.npmrc
Here is the content
registry=https://aus-bin-prd-00.q2dc.local/artifactory/api/npm/virt-npm
@<SCOPE>:registry=https://aus-bin-prd-00.q2dc.local/artifactory/api/npm/virt-npm/
version=2
unsafe-perm=true
That’s all that is necessary to use Q2’s Artifactory instance to pull npm packages
Link to show what is available via the virtual repo