Please do investigate that. Sounds like it would make a great plugin for capistrano.
- Jamis On Jun 17, 2008, at 12:15 PM, Anthony Ettinger wrote: > > There's a program called rsnapshot used for creating hourly backups, > similar pattern may be applicable to deployments. > > I'm currently using the :export option, which makes a duplicate of the > entire tree (even if only 1 file has changed). > > The rsnapshot perl script I'm referring to uses rsync to provide the > delta and only copies files that have been changed, added, or removed. > > It makes a hardlink of all existing files that have not been modified > (saving on disk space) to create the rest of the un-modified tree. > > The advantage is that a deploy could take a few seconds vs. several > minutes, and save on disk space. > > On Tue, Jun 17, 2008 at 3:57 AM, Aníbal Rojas > <[EMAIL PROTECTED]> wrote: >> >> Anthony, >> >> The problem is that there is not a one to one match with the >> deployed application and the content of the SCM. Common deployment >> recipes involve symlinking, generating a version file, etc. Also, >> letting the .svn (in the Subversion case) files in releases/ >> <timestamp> is a security risk, most people sets capistrano to do a >> checkout losing the version metadata. >> >> I understand your point, actually Bazaar has this concept: >> >> $ bzr checkout --lightweight http://whatever >> >> If this were going to be implemented the first thing to solve is >> how to manage the releases/<timestamp> folders, maybe copying the the >> previous release and generating the delta against the new version. I >> need to keep the ability to do rollbacks. >> >> -- >> Anibal >> >> On Jun 17, 12:41 pm, "Anthony Ettinger" <[EMAIL PROTECTED]> wrote: >>> I disagree, why else would you have an scm option to begin with? >>> The whole advantage of using it for a pull scenario is that you can >>> just "svn up" the diff. >>> >>> >>> >>> On Mon, Jun 16, 2008 at 4:19 AM, Aníbal Rojas >>> <[EMAIL PROTECTED]> wrote: >>> >>>> As far as I know there is no support for a "diferential" or "delta" >>>> deploymet. >>> >>>> Its an interesting idea, but seems complex. >>> >>>> -- >>>> Aníbal Rojas >>>> http://hasmanydevelopers.com >>>> http://rubycorner.com >>>> http://anibal.rojas.com.ve >>> >>>> On Jun 16, 1:43 pm, "Anthony Ettinger" <[EMAIL PROTECTED]> wrote: >>>>> Using :export takes quite a long time, even for editing one file. >>> >>>>> Is there a way to only push the difference, and not the entire >>>>> trunk? >>> >>>>> -- >>>>> Anthony Ettinger >>>>> 408-656-2473http://anthony.ettinger.name >>> >>> -- >>> Anthony Ettinger >>> 408-656-2473http://anthony.ettinger.name >>> >> > > > > -- > Anthony Ettinger > 408-656-2473 > http://anthony.ettinger.name > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
