ember-loopback-customers-demo v0.2.0

ember-loopback-customers-demo

A demonstration app with authentication and simple CRUD for customer records, targeting a Loopback backend.

Prerequisites

You will need the following things properly installed on your computer.

• Git
• Node.js (with NPM)
• Ember CLI
• PhantomJS

Installation

• git clone https://github.com/randallmorey/ember-loopback-customers-demo.git
• cd ember-loopback-customers-demo
• npm install

Running / Development

• npm start
• Visit your app at http://localhost:4200.

Code Generators

Make use of code generators. Try ember help generate for more details.

Code Documentation

Code documentation is loosely based on SoftLayer's Ember Style Guide. Follow established documentation conventions demonstrated throughout the repository.

Code documentation is generated by ember-cli-jsdoc. Generated docs are output to docs/ and served from /docs by the ember server for convenience.

• npm run docs

Running Tests

• npm test
• ember test --server

Building

• ember build (development)
• ember build --environment production (production)

Deploying

Specify what it takes to deploy your app.

Contributing

This repository uses semantic-release-cli for automated releases and commitizen and cz-conventional-changelog for standardized commit messages and changelogs.

Committing

All work should be committed to a new topic branch created from develop, never to a mainline branch directly. When ready to commit changes, stage them as usual with git add .. Commit changes with npm, rather than git, in order to ensure standardized commit messages and follow the interactive prompts:

	npm run commit

Note: watch the overview video of commitizen and the conventional changelog tool.

Pull Requests

When a branch is ready to be merged, submit a pull request to develop via GitHub. Pull requests are automatically tested with Travis CI and may not be merged until tests pass. Once tests have passed and the PR has been reviewed, a team member may safely merge the PR into develop.

Releasing

Releases are made from the master branch automatically. To initiate a release, create a PR from develop to master. Releases are automated with semantic-release. An automatic release is tagged and published to npm upon a successful merge into the master branch, after tests pass successfully.