[Capistrano] Re: query_revision - local vs. remote

[Jamis Buck]

This ticket (http://capistrano.lighthouseapp.com/projects/8716/tickets/ 5) was opened a couple weeks ago because of this same issue, where someone wants capistrano to ask the remote host what the revision is, rather than the local host. Feel free to post your comments there; perhaps an idea for a patch will materialize with a bit of discussion.

- Jamis

On May 16, 2008, at 9:38 AM, Erik Kastner wrote:

With this commit:
http://github.com/jamis/capistrano/commit/ec9a7fa52c9f417a9a01a7e764b520be1ec32c5c
the query_revision method was changed from looking at the local tree
(git rev-parse) to the repository (git ls-remote). This breaks my
deploy strategy.

The way I've set up my deploy is to have my origin on github, and a
second repository on the app-server (named app-server). In deploy.rb I
have repository set to  "/var/git/#{application}.git" and a
before_update_code that does git push app-server.

This accomplishes two things:
1) if github is down or slow, it doesn't effect a deployment


However, with the new query_revision, this breaks since I don't have
/var/git/#{application}.git on my local machine. If I change the
:repository to be [EMAIL PROTECTED]:/var.... then I have to have keychain
running as well as the server's public key in it's OWN authorized_keys
file.

I don't mind patching this, I just need to figure out HOW :) (maybe an
option, :deploy_from_localhost or something?)

Thoughts?

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

2) each time I push to the app-server, it's sort of tagging a deployment.

smime.p7s
Description: S/MIME cryptographic signature