[livereload] Started using rack.

And I've stopped invoke WEBrick directly.

WEBrick may still be selected via rack, but it doesn't have to be. For
example-- you can bring 'thin' to the party and rack will pick thin over
WEBrick.
[livereload] Added rake/livereload as middleware
[livereload] Added "listen" for auto-regeneration

This is pretty slime-y-- but I'm just trying to get a sense of this
thing.

Reloads are happening now if I add a Guardfile for 'livereload' and run:

* reveal-ck serve
* guard (livereload)

The goal is to *just* run reveal-ck serve, and figure out how to startup
the equivalent of guard-livereload from there.
[livereload] Added guard-livereload to trigger browse reload
[livereload] Created "Command" classes for Serve/Generate
[livereload] Stopped sending webserver access logs to stderr
[livereload] Refactoring procedural jumble toward OO
[livereload] Moved embedded classes out to distinct files
[livereload] Tweaked 'reveal-ck serve' banner
[livereload] Disabled Guard notifications
[livereload] Created ServeUI
[livereload] Modified "Commands" to use UI
[livereload] Generate "command" now takes a prefix
[livereload] StartWebServer now logs via TempFiles
[livereload] Added a feature around `serve` + capacity to early quit
[livereload] Added explicit requires for tilt adapters
[livereload] Tweaked Aruba settings re: serve feature
[livereload] Preparing release of v0.5.0
[livereload] Increase all Aruba timeouts

..Doing this to mitigate travis-ci build failures via timeout. I thought
this would only happen while testing "reveal-ck serve", but I'm seeing
timeouts in "reveal-ck generate" as well.
[livereload] Modified serve.feature to choose random port