cklist ember install

Ember template installation checklist

• Download the template.
• Unzip and rename the template directory.
• Empty README.md
• Move into the new project and git init.
• Replace all instances of ga-wdi-boston.ember-template with your app name. This includes package.json, bower.json, app/index.html, tests/index.html, and config/environment.js and possibly others. Use the project-find tool in Atom.
• Install dependencies with npm install and bower install.
• Run the development server with ember server. Use the --proxy flag for the local server to avoid writing development-specific CORS (cross-origin resource sharing) and CSP (content security policy) settings.

Structure

• 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.