ember-customers v0.3.0

ember-customers

A simple CRUD application for customer records. View the demo above.

Prerequisites

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

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

Installation

• git clone <repository-url> this repository
• cd ember-customers
• npm install

Running / Development

• ember serve
• Visit your app at http://localhost:4200.

Code Generators

Make use of the many generators for code, try ember help generate for more details.

Running Tests

• ember test
• ember test --server

Building

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

Deploying

Specify what it takes to deploy your app.

Further Reading / Useful Links

• ember.js
• ember-cli
• Development Browser Extensions
  • ember inspector for chrome
  • ember inspector for firefox

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 branch off of 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 merge, submit a pull request to develop via GitHub. Pull requests are automatically tested on Travis CI and may not be merged until all tests pass. At that time, 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. Since releasing is automated, the timing and extent of release PR's is left to the discretion of team members.

Releasing is automated with semantic-release. An automatic release is tagged and published to npm upon a successful merge into the master branch only after all tests successfully pass.