Initial setup

Setting up the basic structure for the repo. There is two top level folders, one is the flask python app, and the other is the ember front end. They are isolated from each other, but can talk to one another too. To run the flask app, change directories into the flask folder and run:

```
$ python app/routes.rb
```

This will run flask's server on http://localhost:5000. Then, in another comand line tab change directories into the ember directory and run:

```
$ ember s --proxy http://localhost:5000
```

This will run the ember server on http://localhost:4200 but it will proxy api requests to flask's server running on port 5000. In this case, I created a simple example of then how to pass json from the flask api to the ember frontend by indexing the ids of the widget ember model served up from the `/widgets` endpoint on the flask server.

Anyway, we'll now have a nice repo structure to place files in appropriately. We can place python library files into the flask app, and then build out any kind of front end we want with either ember or other frontends if we want, too. Folders can demark various aspects of the stack, until they are modular enough to split into their own repos.
Merge pull request #1 from ianstarz/initial-setup

Initial setup
Virtualenv .gitignore

When I first created the repo, I tracked my `virtualenv` files, but we should not do that. People can (and should) use virtualenv to keep a standard set of python dependencies, but let's not track those in the repo.
Merge pull request #2 from ianstarz/virtualenv-gitignore

Good call :) biggest commit I've seen in awhile, so much red.
Merge branch 'ianstarz-master'