humm... It appears to do more or less what cap2 does. My needs are a little different. I would like to use a previously checked out version, that is already on my disk, and tar and gzip it to copy it to the server. It's just that sometimes i need to deploy from my laptop to a customer's server and have no SVN access.
It seems that the best option for me would be to write a custom SCM module. On 5/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Joao, look what i found? > > http://blog.wolfman.com/articles/2006/12/06/a-capistrano-scm-module-for-local-svn-access > > > On May 3, 2:24 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > Hi Jamis. Thanks for the reply. Will def play around there. > > > > If you ever run across the module, please link it and make an > > announcement. There are lots of tortoiseSVN users out there with the > > buggy 'out-of-date' commit problem with SVN that could be eliminated, > > and rails being a framework where lots of programmers are solo, where > > bypassing SVN, but being able to rollback based on the tarball located > > on the client's side would be faster and easer. Perhaps in Cap 5.1? > > > > Thank you for your contributions. > > > > On May 2, 7:15 am, Jamis Buck <[EMAIL PROTECTED]> wrote: > > > > > On May 2, 2007, at 8:11 AM, Joao Nelas wrote: > > > > > > And what about if you don't want to hit the svn server, but instead > > > > deploy from a local working copy? > > > > > That is not supported by the existing deployment code. You'll need to > > > write your own custom tasks, or a custom SCM module for that. > > > > > - Jamis > > > > > > On 5/2/07, Jamis Buck < [EMAIL PROTECTED]> wrote: > > > > On May 2, 2007, at 6:32 AM, [EMAIL PROTECTED] wrote: > > > > > > > I know Jamis is probably working on the tutorial for 2.0. > > > > > > > Can anyone please give share a quick tutorial on the tarball > method > > > > > for deploying? > > > > > > First, set the :deploy_via variable to :copy : > > > > > > set :deploy_via, :copy > > > > > > Then, deploy! > > > > > > cap deploy > > > > > > That will do a "checkout" to a temporary directory, tar+gz it up, > and > > > > sftp it to the remote host(s). If you'd rather use an "export", so > as > > > > not to send all the SCM metadata to the servers, just add: > > > > > > set :copy_strategy, :export > > > > > > Lastly, if you'd rather use zip or tar+bz2 to compress the archive, > > > > rather than tar+gz: > > > > > > set :copy_compression, :zip # or :bzip2 > > > > > > Hope that helps, > > > > > > Jamis > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
