cloud-to-edge-config-ui
This is a web-based UI for collecting the configuration and setup information for the cloud-to-edge project.
Getting Started
This project was generated with
Angular CLI version 6.1.1.
You will need to install Angular if you haven't previously.
For example, on a Mac:
- Install Homebrew (brew.sh)
- Install Node.JS for NPM:
brew install node
- Install the Angular CLI:
npm install -g @angular/cli
- Install other app dependencies:
npm install
The steps on other platforms are similar, but with perhaps a different package manager or a different package name for NPM/Node.
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.
Running the application in a Docker container.
From the root directory
run the node build ng build
to create the 'dist' directory.
run ./docker/runDocker.sh
Browse to http://localhost:4200/
The port can be changed in the runDocker.sh
file
Python 3 Server
The web UI relies on a simple Python backend for data persistence.
Install Python3
Install dependencies
pip3 install flask
pip3 install flask_cors
pip3 install pyyaml
python3 C2EMain.py
Server runs on http://localhost:4201/
Further help
To get more help on the Angular CLI use ng help
or go check out the Angular CLI README.
Contributing
The cloud-to-edge-config-ui project team welcomes contributions from the community. Before you start working with cloud-to-edge-config-ui, please read our Developer Certificate of Origin. All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch. For more detailed information, refer to CONTRIBUTING.md.
License
MIT