Staging

[dornera]

1. Staging environment is all set (I think at least for this project)

-.travis.yml:
- master branch will by default go to staging (there's a comment as this will needed to be changed when merged)
-to push to prod, change env to Hamlet-prod (not ideal since there will be a change but I believe you said this should be ok for now. Just make sure to switch back once pushed to prod)

2. Fixed aws.py allowed_hosts so don't have manual IP addresses and a few typos/wording
3. Removed load balancer config file as it had to point a cert which would change per environment. This is done in Beanstalk in the environment settings and won't change.
4. config.yml removed (no biggie). If we end up using the command line for EB we'll reinitialize each time.

[dornera]

P.S. There was something weird with Travis -> EB deploy so the commits similar to "WTF" and "I don't know" was just an annoying temporary permission fluke which resolved itself

[coveralls]

Coverage remained the same at 88.668% when pulling 1b7ee81 on staging into cca2bcf on master.

[thatandromeda]

Can you squash these commits into something with a descriptive commit message to clean up the history? (https://chris.beams.io/posts/git-commit/ is good if you want a reference on commit messages) After that this is 🌈 👍