A template for starting projects with Ember as a client. Build pipeline and
development server provided by ember-cli. Bootstrap and Sass included.
At the beginning of each cohort update package.json:
- replace all dependent package versions in
package.jsonwith a glob (*). rm -r node_modules.npm update --save.npm update --save-dev.npm install
Currently bower cannot automatically save updated versions to bower.json.
rm -r bower_componentsbower updatebower list- Take the new version numbers from the top level of the list and paste
them into
bower.json bower installember test
Fix errors and conflicts as necessary.
Install build dependencies with npm install. Install runtime dependencies with
bower install.
If you have not installed phantomjs, you will need to install it globally:
npm install --global phantomjs-prebuil
At the beginning of each cohort, update this template by upgrading ember-cli
and generating a new Ember application in another location. Copy files over a
handful at a time and check diffs. You should preserve the pods structure and
other customizations, including Bootstrap.
- Download this template.
- Unzip and rename the template directory.
- Empty
README.mdand fill with your own content. - Move into the new project and
git init. - Replace all instances of
'ga-wdi-boston.ember-template'with your app name. This includespackage.json,bower.json,app/index.html,tests/index.html, andconfig/environment.js, possibly others. - Install dependencies with
npm installandbower install. - Run the development server with
ember server. Use the--proxyflag to avoid writing development-specific CORS and CSP settings.
Build dependencies are stored in package.json. Client
dependencies are stored in bower.json.
Do not configure grunt packages directly in the
Gruntfile.js. Instead, store configurations in the
grunt directory. You won't need a top-level key, since that's
generated by the Gruntfile.js based on the filename of the configuration
object stored in the grunt directory.
Developers should store source code following Ember conventions. This template uses the "pods" layout for organizing code. For an introduction, see Organize Your Ember App with Pods.
Developers should run these often!
grunt nagor justgrunt: runs code quality analysis tools on your code and complainsgrunt reformat: reformats all your code in a standard styleember server: generates bundles, watches, and livereloads (use the--proxyflag when developing locally)ember test: runs any automated testsember build: prepare a distribution for deployment (use the--environmentflag if you've customized builds)ember generate: make use of the many generators for code (tryember help generatefor more details)
- All content is licensed under a CCBYNCSA 4.0 license.
- All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact legal@ga.co.