What happens if you use "/path/to/repo.git" instead of "file:///path/to/repo.git"?
I know I've used local repositories with Capistrano without problem in the past (as long as I'm using a deployment method that doesn't require the remote hosts to access the repository). - Jamis On Thu, Sep 17, 2009 at 10:36 AM, BJ Neilsen <[email protected]> wrote: > > Hi all, > > I'm having an issue deploying a Monk (Sinatra) app to an internal > server here at work using Git. I've setup the git remote repos on the > server that we're deploying to, we'll call it "roger". The issue I'm > coming into trying to deploy:cold is that if I specify > set :repository, "file:///path/to/repo.git", the local ls-remote fails > since that path is relative to the server filesystem. But if I specify > the whole ssh path (Set :repository, "m...@roger:/path/to/repo.git"), > then I have to authenticate every time I deploy. This is still a minor > problem, except authentication fails evertime, even though I can do > normal ssh connections just fine. Is there any way to specify a > local_repos path and remote_repos path? > > Here is the error output from deploy:cold > > > �...@local ~/myapp: cap deploy:cold > > * executing `deploy:cold' > > * executing `deploy:update' > > ** transaction: start > > * executing `deploy:update_code' > > executing locally: "git ls-remote > [email protected]:/path/to/repo.git master" > > [email protected]'s password: > > * executing "git clone -q [email protected]:/path/to/ > repo.git /var/www/myapp/releases/20090917163008 && cd /var/www/myapp/ > releases/20090917163008 && git checkout -q -b deploy > 1af7918b501b0bad10ad4b51853453af224fed89 && (echo > 1af7918b501b0bad10ad4b51853453af224fed89 > /var/www/myapp/releases/ > 20090917163008/REVISION)" > > servers: ["roger.mycompany.com"] > > [roger.mycompany.com] executing command > > ** [roger.mycompany.com :: err] Permission denied, please try > again. > > ** [roger.mycompany.com :: err] Permission denied, please try > again. > > ** [roger.mycompany.com :: err] Permission denied > (publickey,gssapi-keyex,gssapi-with-mic,password). > > ** [roger.mycompany.com :: err] fatal: The remote end hung up > unexpectedly > > command finished > > *** [deploy:update_code] rolling back > > * executing "rm -rf /var/www/myapp/releases/20090917163008; > true" > > servers: ["roger.mycompany.com"] > > [roger.mycompany.com] executing command > > command finished > > failed: "sh -c \"git clone -q [email protected]:/path/ > to/repo.git /var/www/myapp/releases/20090917163008 && cd /var/www/ > myapp/releases/20090917163008 && git checkout -q -b deploy > 1af7918b501b0bad10ad4b51853453af224fed89 && (echo > 1af7918b501b0bad10ad4b51853453af224fed89 > /var/www/myapp/releases/ > 20090917163008/REVISION)\"" on roger.mycompany.com > > So the line "executing locally: "git ls-remote > [email protected]:/path/to/repo.git master"" works fine if > the repository path is ssh, but the remote git clone fails. If I > change the repository path to "file:///..." I suspect it would work if > it got there, but the local ls-remote command fails. > > I can't be the only one who's ever wanted to deploy to the same > machine as the hosted repo, can I? > > Thanks for the help. > BJ > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
