taking advantage of scm for deployment

[Anthony Ettinger]

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-2473
http://anthony.ettinger.name

[Aníbal Rojas]

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

[Anthony Ettinger]

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.

--

[Adrian Madrid]

A crude way of doing it would be to keep a svn/git copy in your prod server, run a update/pull and from the log/output figure out what files changed and copy only those files to the right places. Hope it helps,

AEM

--
Adrian Esteban Madrid
Lead Developer, Prefab Markets
http://www.prefabmarkets.com

[Jesse Proudman]

> 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?

Using Capistrano 2, you can use the set :deploy_via, :remote_cache
variable to have it keep a cached copy and just do an update and copy
from that.

--

Jesse Proudman, Blue Box Group, LLC
http://www.blueboxgrp.com

[Adrian Madrid]

I knew there had to be a better way already made. Gotta check out that option in Capistrano. haven't read their docs in years seems like.


AEM

[Aníbal Rojas]

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

[Aníbal Rojas]

That's it, thanks.

--
Aníbal

On Jun 17, 12:49 pm, Jesse Proudman <jesse.proudman-

[Anthony Ettinger]

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.

--

[Jamis Buck]

Please do investigate that. Sounds like it would make a great plugin
for capistrano.

- Jamis