git clone https://github.com/RedHatInsights/drift-frontend
cd drift-frontend
npm install
npm run start
Ensure the following entry is in your /etc/hosts file:
127.0.0.1 prod.foo.redhat.com
127.0.0.1 stage.foo.redhat.com
127.0.0.1 qa.foo.redhat.com
127.0.0.1 ci.foo.redhat.com
Ensure insights-proxy repo exists in the same parent directory that contains /drift-frontend
https://github.com/RedHatInsights/insights-proxy
In terminal
cd drift-frontend
SPANDX_CONFIG=profiles/local-frontend.js bash ../insights-proxy/scripts/run.sh
In another terminal
cd drift-frontend
npm run start
If you see ℹ ｢wdm｣: Compiled successfully., you are in good shape.
Finally, hit the following URL in your browser. If you are not logged in, you will be prompted to do so.
https://ci.foo.redhat.com:1337/insights/drift
There is already a local-drift-backend.js file in the drift-backend git repo.
Simply run the command below in place of the SPANDX_CONFIG above:
SPANDX_CONFIG=drift-backend/local-drift-backend.js bash insights-proxy/scripts/run.sh
And run the follwing command in another terminal:
npm run start
If you are updating the drift-frontend app after a long period of time away, your node_modules folder may not be up to date with the packages outlined in the package.json file. The easiest way to update this quickly and efficiently is to fun the following commands in a terminal window.
cd drift-frontend
rm -rf node_modules
npm i
After the packages are installed, you should be able to run npm run start in the same terminal to get the app up and running.