Actually having a repository on a remote server is VERY bad practice (IMHO) for security reasons, source code should not be kept on a remote server that is at a colo for instance.
There are many many people who keep the repository on the workstation, or accessible from the workstation, and due to firewalls the server cannot access them. That is why I wrote the local subversion SCM module, it happens to be the only way I can use capistrano to deploy to my servers which are at a remote colo. Judging by the number of downloads this is a pretty popular use case. The next version of capistrano will make this use case much easier, see threads in this group for more info from Jamis on the subject. On Mar 25, 11:40 am, "Ray Baxter" <[EMAIL PROTECTED]> 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. > > -- > > Ray --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
