Check for database configuration before running the deploy

[dkingofpa]

More than once, I've run drush-deploy forgetting to put the database config out there. It happily runs through make and copies the result out to the server only to find that there isn't a database configuration available. Could we fail fast in the case that a database config does not exist?

/usr/local/rvm/gems/ruby-1.9.2-p320/gems/drush-deploy-1.0.9/lib/drush_deploy/database.rb:166:in `throw': uncaught throw #<DrushDeploy::Database::ConfigNotFound: Couldn't locate database configuration default/default. Please check your database configuration.> (ArgumentError)

[medlefsen]

This is an easy fix. I'll include this in 1.1 as well.

Thanks

On Mon 02 Jul 2012 08:43:37 PM EDT, David King wrote:

More than once, I've run drush-deploy forgetting to put the database config out there. It happily runs through make and copies the result out to the server only to find that there isn't a database configuration available. Could we fail fast in the case that a database config does not exist?

/usr/local/rvm/gems/ruby-1.9.2-p320/gems/drush-deploy-1.0.9/lib/drush_deploy/database.rb:166:in `throw': uncaught throw #<DrushDeploy::Database::ConfigNotFound: Couldn't locate database configuration default/default. Please check your database configuration.> (ArgumentError)

---

Reply to this email directly or view it on GitHub:
#4