Here's a pretty boneheaded mistake:
* executing `deploy:assets:precompile' * executing "cd /var/www..." servers: ["mmstaging.deploymentzone.com"] [mmstaging.deploymentzone.com] executing command *** [err :: mmstaging.deploymentzone.com] rake aborted! *** [err :: mmstaging.deploymentzone.com] *** [err :: mmstaging.deploymentzone.com] database configuration does not specify adapter *** [err :: mmstaging.deploymentzone.com] *** [err :: mmstaging.deploymentzone.com] *** [err :: mmstaging.deploymentzone.com] Tasks: TOP => environment *** [err :: mmstaging.deploymentzone.com] *** [err :: mmstaging.deploymentzone.com] (See full trace by running task with --trace) *** [err :: mmstaging.deploymentzone.com]
After which I spent about an hour going round and round finding solutions for Heroku (config.assets.initializeonprecompile = false) and still getting the same error message.
Turns out I just had to push to my remote repository - which included my updated database.yml among other things - because Capistrano pulls that repository as I have configured it to do in my deploy.rb. So you may be running cap staging deploy:cold locally but the repository snapshot on the remote host is going to operate exactly in the way it should.