Moving all components into components folder
21 files changed
tree: 467a0832a870881d5242893bb12b093c7dae900d
  1. .vscode/
  2. e2e/
  3. nginx/
  4. src/
  5. .dockerignore
  6. .editorconfig
  7. .gitignore
  8. .prettierrc
  9. angular.json
  10. db.json
  11. docker-compose.yml
  12. Dockerfile
  13. LICENSE
  14. Makefile
  15. package.json
  16. README.md
  17. routes.json
  18. start.sh
  19. tsconfig.json
  20. tslint.json
  21. yarn.lock
README.md

Yunikorn UI

This project was generated with Angular CLI version 6.1.3.

Development server

Run ng serve 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|guard|interface|enum|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.

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.

Further help

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

Local development

The app depends on json-server for data. Install json-server locally. Run make start-jsonserver to start json-server for local development. Run ng serve to start angular dev server and navigate to http://localhost:4200/.

Docker for production

Run make build-webapp to build the docker image scheduler-web. Run make start-webapp to deploy the container from the docker image scheduler-web. Run make deploy-prod to build and deploy the scheduler webapp using docker-compose. The project uses multi-stage build feature of the docker and requires Docker 17.05 or higher.

Endpoint configurations

The configurations for the endpoints of scheduler and prometheus should be provided in the /assets/config/envconfig.json file. The webaddress can be configured as "hostname:port" or ":port". If there is no hostname provided, the hostname will be inferred from the URL at which the UI is running.