RE: post-commit export
From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Tue, 16 Jun 2009 11:57:55 +0100
> -----Original Message-----
I wouldn't put a WC on the server. I would have a read-only copy of the repository on your network drive that is kept up-to-date with svnsync (which I love BTW). You can then let the users access it via webdav. But... if a working copy is too big, the repo will likely be too big also.
So, why not just export the relevant directories to the network drive regularly? I have a simple script that writes all changed directories to a file as they are committed [for /F "eol=¬ delims=¬" %%A in ('svnlook dirs-changed %1 -r %2') do echo %%A >> c:\svn_exports\export.txt], then at midnight performs some work on these changed dirs (after deleting the non-unique entries). The work you could do is to call svn export on each directory.
Do this every hour, it'll only export those directories that have changed, so it shouldn't take much time to run and you have an almost-current copy.
If space is such a premium, I might also put a property on each folder you want exported, to cut down on exporting some large and/or not-too-useful trees.
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.