Ki-dashboard (pronounced - "Chi") is a fork of angular-fullstack yeoman generators.
Its has few adjusments:
- it is integrated with bootstrap admin 2 dashboard
- it is integrated with ui-router for angular
- its task automation system is gulp
- It uses simple scaffolding with gulp-dogen tool - so you can update & add any scaffold templates relevant to your project right inside the 'gulp' directory (it means - no need for yeoman)
- client & server are decoupled
-
- Eventualy - this repo should include web-components (directives in angular) to create the various widgets available through the bootstrap admin 2 dashboard template
use the built-in gulp dogen
cli to scaffold modules in server & client
- Following the angularjs blog post, follow these Best Practices Recommendations by the angular team
- angularjs development style guide
- angularjs style guide for teams (with a slight diverses in app structure)
- js code styleguide should follow google's js code styleguide
- nodejs code stytelguide should follow the common best practices of nodejs styleguide
- using jshint as global nodejs service:
npm install -g jshint
- The project follows '.jshintrc' as the best practices of node.js styleguide
- Instructions for setting jshint with sublime linter plugin for sublimetext
- Install NodeJS - http://nodejs.org/ or via command line
- Gupljs:
npm install -g gulp
- Bower:
npm install -g bower
- Phantomjs (client testing):
npm install phantomjs
- Karma (client test runner):
npm install -g karma
- for Node Debugging using node inspector:
npm install -g node-inspector
(? install lessnpm install -g less
)
- Run npm to install dependencies
npm install
- Build project (will run bower install, compile less and concat js)
gulp build
- Run the app
gulp
- Test project
gulp test
- Create distribution zip
gulp dist
This command create "distribution zip" file in the "dist" folder.
Process code, raising the server and then activating the project watcher (client side)
gulp
The project is available at http://localhost:8080.
you should run this after running dev-mode:
node-inspector --web-port=8081
open in chrome http://127.0.0.1:8081/debug?port=5858
Please note that you must invoke the build command before invoking dev-mode (one time only).
gulp build
The guideline is to work in a feature branch flow as described well in Github's Scott's blog post
Each feature branch should be named with a prefix of "feature-", so that the automation won't run any tests, build etc.. on these branches.
i.e., a branch for feature of date picker should be named: feature-date-picker
based on angular fullstack yeoman generator