I'm getting the impression that a bundle package, then committing
those packaged gems to the repo and deploying is the way to go. Will
heroku by default look in the vendor/cache directory first before
installing gems remotely?
On Aug 12, 7:14 am, Matthew Todd matthew.t...@gmail.com wrote:
On
On Aug 12, 2010, at 3:34 AM, Bradley wrote:
Right, so I added in:
Host heroku.com
ForwardAgent yes
to my Tomcat user's ~/.ssh/config. This is the user that checks out
from Github then pushes to heroku. I still get the same error,
Permission denied (publickey).
Hi, Brad --
I've just
Right, so I added in:
Host heroku.com
ForwardAgent yes
to my Tomcat user's ~/.ssh/config. This is the user that checks out
from Github then pushes to heroku. I still get the same error,
Permission denied (publickey). Can you explain how this is supposed
to work? I'm confused as to how Heroku
If Bundler is running on Heroku, the Heroku UNIX user account needs to have
its public key in your Github repo as an authorized key.
Each Heroku machine will have a different SSH key generated, and you
non-deterministically deploy to some machine in the Heroku cloud each time
you deploy.
Even if
Hmm... this doesn't seem to work. I was under the impression that
all of the Gem packaging was happening locally, with a git hook, but
it must be happing on heroku's end in a post-receive or something as
you can see it fails with a public key denied. Here's my output:
Fetching
On Aug 10, 2010, at 2:51 PM, Bradley wrote:
Fetching g...@github.com:myuser/mygem.git
Failed to add the host to the list of known hosts (/home/
group_home/.ssh/known_hosts).
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
[31mAn error has
this should be added to the github user's ssh config? I'm not sure i
have that control.
On Aug 10, 8:28 am, Matthew Todd matthew.t...@gmail.com wrote:
On Aug 10, 2010, at 2:51 PM, Bradley wrote:
Fetching g...@github.com:myuser/mygem.git
Failed to add the host to the list of known
On Aug 10, 2010, at 8:28 AM, Matthew Todd wrote:
Host heroku.com
ForwardAgent yes
On Aug 11, 2010, at 7:34 AM, Bradley wrote:
this should be added to the github user's ssh config?
No, to the ssh config of any *local* user (having access to your private GitHub
repository) who needs to run
On Sun, Aug 8, 2010 at 10:23 PM, Bradley bradleyrobert...@gmail.com wrote:
I'm writing a new app that uses a custom gem not publicly available on
gemcutter, or anywhere for that matter. I'm building both the app and
gem with Hudson CI, then I'd like the app pushed to heroku by somehow
If you could package a custom SSH pub/private keypair with your Gemfile, you
could then:
1) Add that pub key to Github
2) Set the :git source in the Gemfile for your private gem to point at your
private SSH Github URL.
However, I don't believe Bundler supports having an embedded public/private
Well my CI server already has access to the github repo (added its key
to github) in order to build my apps/gems, so presumably I should just
be able to use the git source as normal, and when I do the heroku
push, I'm assuming it's this CI user that will be doing the bundling
before pushing to
I'm writing a new app that uses a custom gem not publicly available on
gemcutter, or anywhere for that matter. I'm building both the app and
gem with Hudson CI, then I'd like the app pushed to heroku by somehow
installing this gem and pushing.
I'm a bit confused as to how I might do this. Do I
El 08/08/10 22:23, Bradley escribió:
I'm writing a new app that uses a custom gem not publicly available on
gemcutter, or anywhere for that matter. I'm building both the app and
gem with Hudson CI, then I'd like the app pushed to heroku by somehow
installing this gem and pushing.
I'm a bit
13 matches
Mail list logo
