I can log into my production server (as the same user that's being
used in my deploy.rb file). Then, go to the current release of my
application and run this:
$ rake RAILS_ENV=production db:migrate
...and everything works.
But, if I run cap deploy:migrate (the same command, but through
Capistrano), it fails. ???
Here's my output, cleanup up a bit:
$ cap deploy:migrate
[DEPRECATION] Capistrano.configuration is deprecated. Use
Capistrano::Configuration.instance instead
[DEPRECATION] Capistrano.configuration is deprecated. Use
Capistrano::Configuration.instance instead
[DEPRECATION] Capistrano.configuration is deprecated. Use
Capistrano::Configuration.instance instead
[DEPRECATION] Capistrano.configuration is deprecated. Use
Capistrano::Configuration.instance instead
[DEPRECATION] Capistrano.configuration is deprecated. Use
Capistrano::Configuration.instance instead
* executing `deploy:migrate'
* executing "ls -x /Library/Rails/notify/releases"
servers: ["myserver.com"]
Password:
[myserver.com] executing command
command finished
* executing "cd /Library/Rails/notify/releases/20070802214631; rake
RAILS_ENV=production db:migrate"
servers: ["myserver.com"]
[myserver.com] executing command
** [out :: myserver.com] sh: line 1: rake: command not found
command finished
command "cd /Library/Rails/notify/releases/2007080221
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
