On Mar 25, 2007, at 12:40 PM, Ray Baxter wrote: > On 3/24/07, Scott <[EMAIL PROTECTED]> wrote: > > Seems short-sighted that cap doesn't support local repositories. > > Capistrano is a tool for deploying to remote servers. If you have > remote servers, then you must have a remote repository - remote > either to your application host(s) or to your development host(s). > Therefore you are required to have remote repository set up and > working. > > Why bother to support local repositories if everyone who is using > Capistrano for its intended use will eventually need to set up a > remote repository? That would be short-sighted.
It's actually a pretty valid use-case. Still, for someone to say that cap is short-sighted for not supporting it is just silly. Capistrano was written to support the work we do at 37signals, and it has evolved since to cover a greater and greater breadth of use cases. It will continue to evolve. But it will never meet every person's needs out of the box. At any rate, cap2 will support deployment-via-tarball, which will remove the need for the repo to be remotely accessible. The default will continue to be the checkout-based deployment that currently exists, for backwards compatibility. - Jamis --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
