|Zuul 2ef76e52fc Merge "Add page size of 1000 to preferences"||2 weeks ago|
|bin||1 year ago|
|src||2 weeks ago|
|test||3 years ago|
|.eslintignore||2 months ago|
|.eslintrc||3 years ago|
|.gitignore||1 year ago|
|.gitreview||1 month ago|
|.zuul.yaml||1 month ago|
|Gruntfile.js||2 months ago|
|LICENSE||5 years ago|
|README.md||2 years ago|
|bindep.txt||2 years ago|
|karma.conf.js||2 months ago|
|package.json||5 months ago|
|protractor-integration.conf.js||4 years ago|
|protractor.conf.js||4 years ago|
|tox.ini||3 months ago|
|yarn.lock||8 months ago|
A WebClient for the OpenStack StoryBoard project.
First of all be sure to have tox installed on your machine then:
The following are commands that may be used during project development.
npm run clean: Erases the temporary folders created by various grunt tasks, such as reports, cover and dist.
npm run build: Compile and packages our code.
npm run serve: Development server - runs a build and sets up concurrent watchers that will automatically lint, test, and refresh the code when a change is detected.
npm run test-unit: This command will create a clean build against which our unit tests will be run. For more information, please see karma-unit.conf.js
npm run test-integration: This command will create a clean build against which our functional tests will be run. For more information, please see protractor-integration.conf.js
npm run test-functional: This command will create a clean build against which our functional tests will be run. For more information, please see protractor.conf.js
For more detailed development, the following commands are available via grunt.
To run them, you will need to install grunt globally:
npm install -g grunt.
compile: Compiles all of our sources in the dist directory.
package: Built code into a release package.
serve:dist: This task performs a full build of our application, and then runs that source in a local web server. It does no watching, it simply hosts the files.
serve:prod: This task is identical to ‘server:dist’, with the exception that it will proxy the API requests against the production API. USE WITH CAUTION