Playing with Heroku web dyno and routing to processes on the same dyno - part 1
Playing with Heroku web dyno and routing to processes on the same dyno.  web should run html and api as well as router now
Playing with Heroku web dyno and routing to processes on the same dyno.  Rest of the processes done
Changed API base path for Heroku (seems to be a difference running Swagger on localhost??
Revert "Changed API base path for Heroku (seems to be a difference running Swagger on localhost??"

This reverts commit 0b21f01555f2994c88cbdfcbac36a5cf4f79f0f3.
Swagger UI trailing slash on api lookup
Upstream Site API response.body
Cleaned up startup log output
Added ci environment endpoint for nav json
Correct setting of dev env for tests
More realistic mock nav and html output
Second level nav html endpoint
2nd level; data-parent-uuid
1st level can be requests at /html or /html/plain