add fauxton prototype in a pseudo-working but hokey way. Build (`bbb couchdb`) works (places files correctly into the share dir) but the app doesn't run (I'm guessing because I'm missing some files in the grunt build).
Setup working debug server
Add debug task (couchdebug) for CouchDB that deploys the debug build to the server.
Add dev task to run a standalone node server with the code.
Temporarily disable pushstate to fix initial loading
Properly fix routing and what not

Switch away from push state to hashtags.

Hack to parse query params out of hashtags.

Update all urls in the app to start with #.

Fix router to look for index.html.
Don't need/use the grunt-templater
Add save button to docs
Add support to install as a Couchapp
Merge pull request #1 from garrensmith/fauxton-couchapp

Add support to install as a Couchapp - thanks Garren!
Add logs module to display couchdb logs in Fauxton
add missing log template
Merge pull request #2 from garrensmith/fauxton_logs

Add logs module to display couchdb logs in Fauxton
Changing "Install as Couchapp" instructions

The instructions didn't work for me. I also prefer not installing node modules globally.

I also removed the step of building CouchDB as I'd expect most people that want to run it as a CouchApp already have a couch installed.
router removes previous dashboard, cleanup log parsing, fix grunt tasks for debug to worklike release
Merge pull request #3 from vmx/patch-1

Changing "Install as Couchapp" instructions
Not all lint warnings are errors, fix query parsing
Add tbody to logs table for bootstrap styling
Merge pull request #4 from garrensmith/router_clean_up

Router remove(), log clean up and fix couchapp grunt tasks
Update layout manager to 0.7
Abstract dashboard layout construction

This moves the construction of the dashboard layout into the
initialization function of the router and adds some helper functions
to allow you to specifically set the dashboard content or the
breadcrumbs content, removing a lot of the duplication in generating
the base layout.

The setDashboardDom function is a bit hacky and we should look for a
better approach.

I updated where the Logs view is binding onto the reset event, so that
it happens after the first render, as we want the layout to do the
initial first render of the Logs view, and then update the view when
new logs come in.

I moved the remove logic into setDashboardContent which will remove
the old view which properly triggers the cleanup function in the logs view.