Thanks for the tips. I got into bash and ran through the steps manually. But there's still something really odd going on:
~/test $ export GIT_SSH="/app/bin/git_ssh.sh" ~/test $ git push [email protected]:misterdai/test.git master:gh-pages --force error: cannot run /app/bin/git_ssh.sh: No such file or directory fatal: unable to fork ~/test $ ls /app/bin git_ssh.sh node So it still seems like when git reads the GIT_SSH var, it can't find git_ssh.sh, even thought it's right there? Getting pretty confused. I do have a workaround of setting up another github account and using https://username:password@github etc... But preferred the idea of using a deploy key to restrict access to a single repository. Dave On Thursday, 4 April 2013 10:39:10 UTC+1, Daniel Farina wrote: > > On Thu, Apr 4, 2013 at 1:36 AM, David Boyer > <[email protected]<javascript:>> > wrote: > > Didn't get chance to try it out from home but I'm sure it's probably a > > firewall not letting me out. If I try it on an external connection and > > still have issues I'll log it on the off chance ;) > > Unfortunately I found the issue; it has been closed with, basically, > 'arrrgh'...but I'd go there and register your +1 that this sucks and > it'd be nice to find some way to get around this: > > https://github.com/heroku/heroku/issues/407 > > > From all the variations I've tried so far it feels like the following > > happens: > > > > git commands fire off fine (git init, git add, git commit) > > git push to github starts > > > > It spots the GIT_SSH environmental variable. > > Reads it correctly. > > Can't find the file /app/git_ssh.sh error (unable to fork) > > > > It's really weird, because that file definitely exists. It's almost > seems > > like the git process spawns "sh" to run the script but it can't see the > /app > > mount? I'm grabbing at straws if that sounds daft ;)> > > Well, I don't think we do anything unusual there -- perhaps you should > try stepping through it while running inside 'heroku run bash'? > > I know the 'heroku run bash' to get a shell hooked up from a Heroku > container to your local TTY is old news by now, but I feel inclined to > remark that it's saved me enormous grief in debugging this kind of > thing: so before tearing one's hair out I'd strongly recommend somehow > making 'heroku run bash' happen. > > Also, there is a convention of putting executable utilities into > "/app/bin", which in a local git repository is rendered as > REPO_ROOT/bin. That shouldn't break your stuff, but I think parts of > the toolchain anticipate it...for example, $PATH in an environment > emitted from the Ruby build pack (not every buildpack does this or > needs to): > > /app/bin:/app/vendor/bundle/ruby/1.9.1/bin:/usr/local/bin:/usr/bin:/bin > > Doing this, you can take advantage of up things in ./bin/ in your > repository (translated to /app/bin on Heroku) being in $PATH from the > get-go, at least for Ruby. > > -- > fdr > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
