I ended up solving it a different way: I redefined deploy:migrate to run against the primary :app role instead of :db. Seems to work!
On Jan 15, 2:48 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > My apologies for not getting back to you sooner. What I meant was to > use the ssh command-line itself, directly, to set up the tunnel. Then, > once the tunnel is in place, you'd define the role in Capistrano like > this (the example here assumes you set up the tunnel on port 12345 of > the localhost): > > role :db, "[EMAIL PROTECTED]:12345" > > - Jamis > > On Jan 6, 2008, at 9:00 PM, jemminger wrote: > > > > > jamis, thanks for your reply. > > >> Capistrano does not (yet) support a gateway per server. If you need > >> something like that, you can work around cap's limitation by setting > >> up the tunnel yourself (using ssh), and then specifying > >> [EMAIL PROTECTED]:port as the host for that specific server. > > > can you elaborate? i'm not quite sure how to do that in cap. > > specifically i'm trying to run 'rake db:migrate' on the db server > > (which requires a different user and an ssh tunnel) > > > > > > > smime.p7s > 3KDownload --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
