Sample report from an integration test:
https://saucelabs.com/beta/tests/7e6958fd51d44abfbb7a5e7a1efe132a/commands
See, e.g., screencast that you can play or see history.

This simplifies Dockerfile and fixes bugs where it would produce errors
on build.

Fixes #315

I propose that we start with version 0.1 and use semantic versioning.

* now it is possible to build and push images to gcr.io with gulp
* there's yaml file to run the dashboard in your cluster with kubectl create -f

This speeds up our Travis CI infra by like 50% and deletes lots of code (which is a benefit).

Learn more at: http://kubernetes.io/v1.1/docs/getting-started-guides/docker.html

This is to prevent flakyness in our travis infrastructure.

This PR implements column layout for the replica set list view. The
layout is implemented through a directive that puts its transcluded
elements into a column layout.

There's some algorithmic code in this PR, so please comment if something
is not tested or easy to understand.

Please also verify on your machines that this works correctly.

This speeds up serve:prod task a few times, yet has the same effect.
Backend:prod should only be used in dockerfiles.

They just have been recently added. It allows us to delete some code.

This change adds linter for styles to the project and updates all styles
to conform with the default set of rules.

This should help us maintain a little bit more consistency in our
styles.

Previously only bottom half was being executed. This was caused by
duplicate keys. I've moved postinstall to a script.

BREAKING CHANGE: Now node 4 is required to build the project. This is
because protractor 3 requires is. I decided to make the switch now,
because it would happen anyway at some point.

This change handles replica set description end-to-end: saving in on the
deploy form and then displaying. It also handles replica set endpoints.
I also attempted to write tests for the go code, but this change grew
too much. I'll do this later.

With this I can work with `kubectl proxy` clusters. Everything else
stays the same.

This was caused by the wait-for-cluster rule which never finished.
I've moved it to local-up-cluster. Everything works now as expected.

With this change I've gone through all ESLint rules at:
http://eslint.org/docs/rules/ and added all of them that I feel make
sense to the project.

This will allow us to focus on business logic of our code, rather than
on style discussions, which are now better guarded thanks to ESLint and
clang-format.

On the final note: it does not matter what concrete lint rules are
enforced (e.g., semicolons or nor). The important part is that they are
enforced by a tool and we do not spend time dicussing about them.

Addresses: #66

This change reformats all files according to clang-format rules (the
same that Angular JS has) and forces the files to comply with the
formatting.

This change connects replica set list and detail views and applies
RESTful conventions to the API.

Now API and app URLs follow RESTful API conventions. This change is also
an example of how views hould be connected. See state params and state
name exports.

Without this fix, `gulp serve` fails.

Now it is correctly specified and allows for imports anchored at
frontend src, e.g., `import 'chrome/chrome';`.