Make sure to set your deploy key on GitHub to the public key of your deployment user. You'll find this in the "Admin" section of your repository. If that fails, I'd suggest using the copy strategy:
set :deploy_via, :copy set :copy_strategy, :export That will avoid the deploy key issue altogether. Sean andres wrote: > Hi, > > another newbie question, > > I use a github account with a private repo, > thus shh key at the target server needs to be loaded, > for git to work. > > what's the preferred approach when capistraning? > > adding a new keyless shh-key and have a task running sometghing like? > exec ssh-client bash > ssh-add .ssh/unprotected key > > or run another git repo probably over http? > > thanks again, > > > Andres > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
