I'm in the middle of an Engine Yard slice deployment. The guys have
emailed me saying they had problems with my repo access (I said in the
sign-up settings that it was a private repo and that I thought the
only solution to this was to add someone as a collaborator), is there
a way to allow access to the repo without making it public; am I
missing something here?
Also, related to this, I'm using EY Express slice on my MBP for local
staging. I just tried the cold deploy and I hit a roll back after
capistrano tries to reach GitHub. This is probably related to the
private access on the repo;
* executing `express'
triggering before callbacks for `deploy:long'
* executing `deploy:long'
** transaction: start
* executing `deploy:update_code'
* executing "git clone [EMAIL PROTECTED]: {I've censored the rest of
this}
servers: ["{and I've censored this too}"]
*** [deploy:update_code] rolling back
* executing "rm -rf /data/merb/releases/20081001095438; true"
servers: ["{censored}"]
** [deploy:update_code] exception while rolling back:
Capistrano::ConnectionError, connection failed for: {censored}
(Errno::ETIMEDOUT: Operation timed out - connect(2))
connection failed for: {censored} (Errno::ETIMEDOUT: Operation timed
out - connect(2))
For quick reference, the cap recipe included with the Express slice
looks like this;
#
==============================================================================
# DEPLOYING USING GITHUB
#
==============================================================================
set :github_user, "YOUR_GITHUB_USER"
set :github_app, "YOUR_GITHUB_APP"
set :scm, :git
# Replace this with your git repository name
set :repository, "[EMAIL PROTECTED]:#{github_user}/#{github_app}.git"
# Replace this with your git username
set :scm_user, github_user
# Leave this, as we deploy and run the applications on the VM image as
'express'
set :user, 'express'
# This is the branch you wish to deploy, by default we've set it to
master,
# however you might want to set it to 'stable' or some other branch
you're using
set :branch, "master"
# Deploy using an ssh agent. On Mac OS X you may need to run:
# or something similar, to add your key to the agent and run it
# ssh-agent; ssh-add ~/.ssh/id_dsa
set :ssh_options, { :forward_agent => true }
...and this is what it looks like after I've made my changes;
#
==============================================================================
# DEPLOYING USING GITHUB
#
==============================================================================
set :github_user, "neilcauldwell"
set :github_app, "myapp"
set :scm, :git
# Replace this with your git repository name
set :repository, "[EMAIL PROTECTED]:neilcauldwell/myapp.git"
# Replace this with your git username
set :scm_user, github_user
# Leave this, as we deploy and run the applications on the VM image as
'express'
set :user, 'express'
# This is the branch you wish to deploy, by default we've set it to
master,
# however you might want to set it to 'stable' or some other branch
you're using
set :branch, "master"
# Deploy using an ssh agent. On Mac OS X you may need to run:
# or something similar, to add your key to the agent and run it
# ssh-agent; ssh-add ~/.ssh/id_dsa
set :ssh_options, { :forward_agent => true }
Any ideas?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to github@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---
