opendev
/
storyboard-webclient
Code Issues Proposed changes
OpenStack Task Tracking Browser Client
279 Commits 1 Branch 0 Tags 8 MiB
JavaScript 53.4%
HTML 41.1%
SCSS 4.3%
Shell 0.6%
Smarty 0.5%
Go to file
Jeremy Stanley 40d06c9cf0 Workflow documentation is now in infra-manual 
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.

Change-Id: Ibedb78a5054bde62a6f55d8a40a6dcb9e99578a4
 		2014-12-05 03:30:43 +00:00
bin Removed nodeenv dependency 2014-08-12 17:02:07 -07:00
src Workflow documentation is now in infra-manual 2014-12-05 03:30:43 +00:00
test Merge "Added configuration file for docs-draft." 2014-09-29 19:06:30 +00:00
.gitignore Favicon Whitelabel 2014-04-24 10:59:05 -07:00
.gitreview Initial commit 2014-01-14 18:49:39 -08:00
.jshintrc Added unit tests for string_util. 2014-03-28 16:57:32 -07:00
Gruntfile.js Switch to "serve" verb. 2014-11-07 11:29:16 +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 Auth support 2014-03-03 13:56:11 -08:00
karma-unit.conf.js Added unit tests for string_util. 2014-03-28 16:57:32 -07:00
package.json Fixed gifcicle version 2014-11-04 03:25:54 +01:00
protractor.conf.js Updated build tool versions 2014-10-01 11:36:54 -07: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