Generally, the answer is to not put your actual DB server in the :db role, but instead just choose one of your other servers. The :db role is only used to determine which server migrations are run from, so it can be any of your servers that have access to your database.
- Jamis On 8/12/07, Paul <[EMAIL PROTECTED]> wrote: > > I'm having the same issue ... what was the answer? Thanks! > > On Jun 25, 12:11 am, fenton <[EMAIL PROTECTED]> wrote: > > found the answer...thx. > > > > On Jun 24, 8:46 pm, fenton <[EMAIL PROTECTED]> wrote: > > > > > In my config/deploy.rb I have, > > > > > role :db, "mysql.spicevan.com" > > > > > which is a database server I don't have shell login permission to. > > > Therefore the 'cap setup' command fails because it tries to login to > > > that machine. I'm connecting fromwww.spicevan.comto > > > mysql.spicevan.com in my rails app, should I set my db role to > > > "www.spicevan.com"? > > > > > confused... > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
