OpenStack Task Tracking Browser Client

Go to file

Marton Kiss 8f2781e31b Replace Firefox with Chrome in selenium tests functional tests with Firefox 35 are broken due this open FF issue: https://code.google.com/p/selenium/issues/detail?id=8390 Chrome and FF 34 works well, but need to use Chrome because we cannot pin FF to 34.0 in test instances. Chrome must be added to test jobs also. Change-Id: I53d819b78aca26fddbebfc250d2f4dfb4e29ec74		2015-01-21 14:50:43 +01:00
bin	Removed nodeenv dependency	2014-08-12 17:02:07 -07:00
src	Merge "Add grunt-lintspaces module to check cr-at-end in js files"	2015-01-12 10:28:34 +00:00
test	Add grunt-lintspaces module to check cr-at-end in js files	2015-01-07 13:29:23 +01:00
.gitignore	Eabled custom dev configuration.	2014-12-01 07:18:07 -08:00
.gitreview	Initial commit	2014-01-14 18:49:39 -08:00
.jshintrc	Add grunt-lintspaces module to check cr-at-end in js files	2015-01-07 13:29:23 +01:00
Gruntfile.js	Add grunt-lintspaces module to check cr-at-end in js files	2015-01-07 13:29:23 +01:00
LICENSE	Initial commit	2014-01-14 18:49:39 -08:00
README.md	Workflow documentation is now in infra-manual	2014-12-05 03:30:43 +00:00
bower.json	Enable HTTP Caching on resources.	2014-11-24 14:11:46 -08:00
karma-integration.conf.js	Add grunt-lintspaces module to check cr-at-end in js files	2015-01-07 13:29:23 +01:00
karma-unit.conf.js	Add grunt-lintspaces module to check cr-at-end in js files	2015-01-07 13:29:23 +01:00
package.json	Add grunt-lintspaces module to check cr-at-end in js files	2015-01-07 13:29:23 +01:00
protractor.conf.js	Replace Firefox with Chrome in selenium tests	2015-01-21 14:50:43 +01:00
tox.ini	Removed nodeenv dependency	2014-08-12 17:02:07 -07:00

README.md

Storyboard Web Client

A WebClient for the OpenStack Storyboard project.

Project Resources

Getting Started

First of all be sure to have tox installed on your machine then:

Install the virtualenv containing nodejs: tox -evenv
Source the new path containing grunt: source .tox/venv/bin/activate
Now you can launch the grunt tasks of storyboard-webclient, by default run the development server with the following command: grunt server

Grunt tasks

Here are the grunt tasks available with the storyboard-webclient project, the following commands must be prefixed by grunt, example for the first one, the command to run will be grunt jshint, the virtualenv must have been activated see previous section:

jshint: Runs a linter on the javascript sources files of the project, this will help us keeping style consistency across our files and can reduce the risk of bugs.
clean: Erases the temporary folders created by various grunt tasks, such as reports, cover and dist.
less: Compiles the themes files present in /src/theme/custom and /src/theme/custom using less compiler, the result which is a plain css file is stored into dist/styles/main.css
compile: Compiles all of our sources in the dist directory.
package: Built code into a release package.
build: Compile and packages our code.
server: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.
server: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
server: Development server - runs a build and sets up concurrent watchers that will automatically lint, test, and refresh the code when a change is detected.
test: Run all the tests.
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
test:integration: This command will create a clean build against which our integration tests will be run. For more information, please see karma-integration.conf.js
test:functional: This command will create a clean build against which our functional tests will be run. For more information, please see karma-functional.conf.js