On Tue, 2004-11-30 at 16:35 +1300, Michael Stevens wrote:
> Hello, just thought I'd jump in here... Am I right in assuming that:
>
> a) Every time you deploy, you checkout a new copy of your repository,
> and then FTP it to the server?
> b) The FTP client is checking the timestamps on your fresh working
> copy, vs the timestamps on the server?
> c) The timestamps of the newly checked out repository are all newer
> than the timestamps on the server (being that the timestamps have all
> been set to what was recently checked out), so the entire working copy
> is being copied, rather than the changes?
>
> If that is the issue, then perhaps I can suggest a simple solution.
> Maintain a working copy of the repository (lets call this the staging
> copy), don't delete it when you've done deploying. Don't checkout a
> new copy each time. Rather, simply run 'svn update' on your staging
> copy. Only new files will be updated, so timestamps should only
> change on the files that have actually been updated. After that FTP
> your staging copy to your server.
>
> We use this exact solution here at work (albiet with a complex file
> comparision tool someone hacked up in Perl, rather than a simple FTP
> client), and it works just fine.
We go one step further than that - we have a working copy on the web
server that is updated by a hook script whenever something is checked
in, and a 'make' is run in it (to do xslt transforms to create the
static web pages). The output files from that transform are visible as
a 'staging' server, and then a cgi on the main site uses rsync to move
any changed files to the real web site.
Each step only touches files that have actually changed, and all
dependencies are accounted for.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 4 21:44:50 2004