flattening the project structure, all elixir server side code will be done in a separate repo to allow taking advantage of travis-ci
remove grunt based npm deps, pointed threejs to r66 so we know what version everyone is on, pointed ember to canary since we need that for the query params features this also avoid issues when installing or updating bower deps. also the testem config at least tries to run tests, fails right now since there are none
first stab at getting travis ci integration
oops actually for our tests we don't need our api stub server. all tests should be using the test fixture adapter
with the bower.json pointing to ember#canary we don't need to keep track of it ourselves any longer
pulling down three.js on every CI eats a lot of time. it d/l's about 80-100 megs it seems so lets just commit it
unneeded resolution for jquery in the bower.json... well at least bower thought so after a
let testem return a successful result for now
adding a wait to the ci to see if firefox exiting is due to xvfb not being completely started
ok lets simplify and since install bower and our dependencies takes so damn long, lets try starting xvfb before that
Merge pull request #14 from voluspa/issue/9.travis.ci

flatten project structure and enable Travis-CI support