Engage-lib NPM

AlpsEngage

This project was generated with angular-cli version 1.0.0-beta.24. The latest angular-cli version this project is built using 6.0.3

Development server

Run npm start for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.

Production build

Run ng build --prod

Run

Run npm start

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor. Before running the tests make sure you are serving the app via ng serve.

Further help

To get more help on the angular-cli use ng help or go check out the Angular-CLI README.

Docker Image Setup

Create the engage base image, docker file present (ENGAGE/base-engage/Dockerfile) docker build -t lucasware.azurecr.io/alps/core/engage/base:develop .
Create the main engage image from root directory (ENGAGE/Dockerfile) docker build -t lucasware.azurecr.io/alps/core/engage:develop .

Note

To test the application running locally against the Angular CLI dev server with an external (non-localhost) browser, change the line under scripts->start in package.json to "start": "ng serve --proxy-config proxy.conf.json --host 192.168.2.198", where the IP is the address of the local machine. Also, change the environment.ts file to use the same IP address in the baseUrl.

To test the application running locally against the Angular CLI dev server and the back-end services running on something other than localhost, change the line under scripts->start in package.json to "start": "ng serve dev-engage --host [HOSTNAME] --disableHostCheck true". Also, change the environment.ts file to use the appropriate HOSTNAME value in the gatewayUrl and baseUrl:AlpsGateway configurations.

If your running into issue with package load issue temporarily disable Symantec protection Symantec virus dashboard > disabling Network and Host Exploit mitigation's > options> disable network threat protection (Note: Make sure to turn it back on once your docker setup is done)

Open the windows docker desktop application, click on the setting gear icon > Docker Engine, configure the DNS setting as below DNS:8.8.8.8 & 1.1.1.1, hit Apply & restart button