On Thu, Feb 5, 2009 at 5:46 AM, Lee Hambley <[email protected]> wrote:
> > To work like this, You'll need to use the "copy" strategy, which just > uploads a copy of the code to the server, or you may be able to tell your > server how to reach your laptop, but that is asking for trouble with NAT & > Firewalls. > That makes no sense. I haven't looked at the official strategies for awhile, but the one I wrote just did a "git push" from local dev directly to the server -- no messing with NAT or Firewalls, if you can ssh into the server, and it has Git installed, you can git push to it. It would push to a shared, cached copy, and would then clone to each release -- the "clone" step was absurdly fast, as Git will use hardlinks where it can. It has the added benefit that if you're deploying something like Mephisto, which allows admins to change files on the server, you can commit those changes back to that repository and pull them back down. If anyone wants my strategies, I'd be happy to publish them, but they looked very similar to what the official remote_cache strategy is doing, so I haven't bothered. Oh, to summarize: No GIthub needed, no firewall munging or port-forwarding hackery needed. You just have a server with Git installed, and if you can ssh to it, you're good. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
