opendev/storyboard-webclient
Code Issues Proposed changes
OpenStack Task Tracking Browser Client
863 Commits 1 Branch 0 Tags 8 MiB
JavaScript 53.4%
HTML 41.1%
SCSS 4.3%
Shell 0.6%
Smarty 0.5%
67cb1eb57c
Go to file
Adam Coldrick 67cb1eb57c Rebuild node-sass bindings when running the webclient dev server 
If a newer version of node.js is installed on the user's system than is
used in tox.ini, it is possible to run into errors when running the
sass-related parts of the build. Forcing a rebuild of the bindings
fixes this issue.

Change-Id: Ia4dc046334d4c483f0a880f158bdfa56c153a199
2019-02-03 19:42:25 +00:00
bin Remove bower and add yarn support 2017-12-23 10:40:35 -06:00
src Handle project names in the new Story modal controller 2018-10-23 19:47:00 +01:00
test Make the docs-draft build point to storyboard-dev 2016-05-19 14:19:55 +00:00
.eslintignore Remove bower and add yarn support 2017-12-23 10:40:35 -06:00
.eslintrc Render descriptions and comments as Markdown 2015-09-22 10:04:53 +00:00
.gitignore Remove bower and add yarn support 2017-12-23 10:40:35 -06:00
.gitreview Initial commit 2014-01-14 18:49:39 -08:00
.zuul.yaml Upgrade node version in tests to 6 2018-02-27 08:47:58 +00:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 19:31:07 +02:00
Gruntfile.js Revert "Add transpiling as a step in the build process" 2018-09-11 15:29:26 +00:00
karma.conf.js Remove bower and add yarn support 2017-12-23 10:40:35 -06:00
LICENSE Initial commit 2014-01-14 18:49:39 -08:00
package.json Change openstack-dev to openstack-discuss 2018-12-15 15:52:07 +08: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 Rebuild node-sass bindings when running the webclient dev server 2019-02-03 19:42:25 +00:00
yarn.lock Revert "Add transpiling as a step in the build process" 2018-09-11 15:29:26 +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