Enhanced error message on app deploys missing db

When deploying for the first time there is no database present. If a customer's application relies on a database connection for deploy it will fail. We can give instructions to mitigate this issue to users who encounter this error.
Merge pull request #235 from heroku/schneems/db-bootstrap

Enhanced error message on app deploys missing db
Enhanced error message on app deploys missing db

When deploying for the first time there is no database present. If a customer's application relies on a database connection for deploy it will fail. We can give instructions to mitigate this issue to users who encounter this error.
Merge pull request #236 from heroku/schneems/db-bootstrap

Enhanced error message on app deploys missing db
bump to v110
v110
spelling
don't make :publish public
v111
bump to v111
use ENV variables to configure vendor_url as sometimes we have an internal vendor mirror
Avoid "Running: rake assets:precompile" stutter in build pack output

To fix this, use a distinct title intended to convey the purpose of
the step to humans, using the same jargon as the completion message
("asset precompile").

As seen in Rack applications, this banner would appear as follows:

-----> Running: rake assets:precompile
       Running: rake assets:precompile

Normally, the banner and the performed command are different, e.g.:

-----> Installing dependencies using 1.5.2
       Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
bump libyaml to 0.1.6 for CVE-2014-2525
update changelog
bump to v112
Merge pull request #241 from fdr/fdr-asset-precompile-topic

Avoid "Running: rake assets:precompile" stutter in build pack output
Merge pull request #238 from yangchenyun/master

use ENV variables to configure vendor_url
fix tests
Parametrize curl connect timeout.
Merge pull request #253 from heroku/schneems/remove-user-env

fix tests