OpenStack Task Tracking Browser Client

Go to file

Adam Coldrick a33bb27f10 Allow teams to be added to the permission list for private stories This commit adds a way to add teams to the permission list for private stories. This makes it easy to use for stories that should only be visible to a given set of people; the members of that set can now be managed by the teams UI rather than on a per-story basis. Change-Id: I7d3adde5d6cf9b4d5b7e63df06d2266f7b824666 Depends-On: I16a7451e8c24da352357abb0590d0ace5b4e77f4		2016-12-07 21:11:52 +00:00
bin	Removed nodeenv dependency	2014-08-12 17:02:07 -07:00
src	Allow teams to be added to the permission list for private stories	2016-12-07 21:11:52 +00:00
test	Make the docs-draft build point to storyboard-dev	2016-05-19 14:19:55 +00:00
.eslintignore	Removed grunt:eslint in favor of just running eslint	2016-04-12 07:29:06 -07:00
.eslintrc	Render descriptions and comments as Markdown	2015-09-22 10:04:53 +00:00
.gitignore	Display the most recent commit SHA on the about page	2015-12-16 15:41:39 +00:00
.gitreview	Initial commit	2014-01-14 18:49:39 -08:00
bindep.txt	Move other-requirements.txt to bindep.txt	2016-08-12 19:31:07 +02:00
bower.json	Include moment-timezone to stop all the warnings about it	2016-06-01 12:53:27 +00:00
Gruntfile.js	Removed grunt-bower	2016-06-06 09:13:44 -07:00
karma.conf.js	Renamed karma-unit.conf.js	2016-05-18 16:54:01 +00:00
LICENSE	Initial commit	2014-01-14 18:49:39 -08:00
package.json	Removed grunt-bower	2016-06-06 09:13:44 -07:00
protractor-integration.conf.js	Initial proposal for integration tests	2015-04-07 11:05:19 +02:00
protractor.conf.js	Enabled eslint:strict	2015-03-16 14:02:36 -07:00
README.md	Add Worklists and Boards to About Page	2016-08-17 01:00:18 +09:00
tox.ini	List system dependencies for running common tests	2016-06-28 09:18:49 +00: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 serve

NPM Commands

The following are commands that may be used during project development.

npm run lint: 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.
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

Grunt tasks

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