I see this:
* executing "cd /home/{user_name}/{app_name}/releases/20080325163731; rake RAILS_ENV=production db:migrate"
servers: ["{server}"]
[{server}] executing command
** [out :: {server}] (in /home/{user_name}/{app_name}/releases/20080325163731)
** [out :: {server}] rake aborted!
** [out :: {server}] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
** [out :: {server}]
** [out :: {server}] (See full trace by running task with --trace)
command finished
My production database.yaml looks like so: production:
adapter: mysql
database: {account}_{app_name}db
user: {account}_user
password: pw
# host: localhost
# socket: /var/lib/mysqlsock/mysql.sock
timeout: 5000
I feel like I've tried every permutation possible for the prod db set-up and yet the cap deploy:cold still fails in the rake section as does running:rake RAILS_ENV=production db:migrate --trace
When I try and run it from: /home/{user_name}/{app_name}/current (in /home/{user_name}/{app_name}/releases/20080325163731)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:migrate
rake aborted!
Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
I feel like this has to be something easy, but at this point I'm just at a loss.My hope is that once I can get this straightened out I'll be able to get to the bottom of the "Application error Rails application failed to start properly" error I'm getting ...
Any pointers would be excellent.
-Tom