Scott,
perhaps you can use these ramblings - otherwise just shake your head
ever so slightly and sigh, please ;)
if there were a "local" strategy - then configuration settings could
signal whether local would mean local as in "my local client where I'm
developing and therefore has a checked_out branch which I'd like to
use" or local as in "the app server where my source code eventually
should perform greatness to all good men and true to DRY-ness
therefore I have placed my shared repository on the same server"
the command to exec would be - to the best of my limited insight into
capistrano:
1. git clone #{repository} somewhere; cd somewhere
2. git checkout -b deploy HEAD; cd ..; mv somewhere #{releases_path}/
#{timestamp}
I'm not 100% sure about the HEAD thing - best keep it the way
capistrano does otherwise - but apart from that - this should fly :)
cheers,
walt
ps. your suggestion for a temporary "fix" sure is valid - but in my
scenario, I have a firewall which I'm being eased through - on port 22
and I'm not allowed to establish connections outbound - and no other
machine on the inside to "mistreat" - and to make it perfect: I'm on a
public key, so not matter how much I'd like to do just what you
suggested, I don't see how I could ...
guess I'll just sit tight and hope for you to prevail :)
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
