On Jan 24, 2006, at 18:26, Kalin KOZHUHAROV wrote:
>> Is the repository on a different machine than the web server? Does
>> the
>> repository server have spare disk space? If so, then I would keep a
>> complete working copy of the relevant subset of the repository on the
>> repository server and update it whenever a relevant commit occurs.
>> Then
>> I would use rsync to synchronize this with the directory on the web
>> server. rsync will only send the changes over the network, so it
>> would
>> be comparable to running svn up.
>
> It will be even faster, IMHO and you can exclude the .svn files
> like this:
>
> $ alias R='rsync -Hazv --delete --delete-after --progress --
> exclude=.svn/'
> $ R working_dir/ webserver.domain.org:html/
>
> I am actually using sort of this but without the hook: not frequent
> updates
> so for now manually running the rsync is OK.
Er... yes... I seem to have forgotten that part. Either use svn
export on the working copy first, then rsync the export, or just
exclude the .svn directories when rsyncing the working copy. The
latter is probably quicker, because you don't have to wait for the
export, and apparently easy, as shown above.
>> If, on the other hand, you only have a single server which is
>> handling
>> both repository and web server, and this is the server with the
>> constrained disk space situation, then I don't know a solution.
>
> Then use file:// and have the repo on your workstation :-) If you
> dare.
And if you have the repository on your workstation, then you do not
have the repository and the web server on the same machine, hence
we're back to the first scenario and you can follow the above
recommendations.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 24 18:52:24 2006