Re: Re: TortoiseSVN-1.5.0-RC2 released

Hi John,

On 22/05/2008, Ed Avis <eda_at_waniasset.com> wrote:
> Fisher, John <jfisher@...> writes:
>
>>Each person should have local working copies. The shared location
>>should not be touched directly by any user not logged on directly to the
>>machine with the files (so they all would have the same version of
>>TortioseSVN).
>
> I wanted to do this but I couldn't get TortoiseSVN to install on the server,
> so
> I settled for updating it via a network share. Perhaps I should try again
> to
> install it.
>

The server side needs subversion installed and a post-commit hook that
will then do an update (or export) of the folder(s) you are interested
in. The contents of the hook script depend on the server platform, but
there should be plenty of samples available (there are hook templates,
scripts in the contrib folder, and searching on Google will
undoubtedly turn up even more).

>>To make this work, you could set up an automated process that watches
>>for changes to the related subversion folder, and does an update on the
>>shared configuration folder.
>
> Well, not automated, we still want a manual step before changes are released
> to
> production. But yes there could be a setup like that.

That can be handled by tagging or SVNcopying the approved changes to a
branch and having the post-commit hook watch the 'production' branch.

-- 
Regards,
Jean-Marc
----------------
    ___
   // \\  @@     "De Chelonian Mobile"
  / \_/ \/._)    TortoiseSVN
 <\_/_\_/ /      The coolest Interface to (Sub)Version Control
  /_/   \_\      Check out http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org