On 31 May 2012 12:03, Steve Swift <steve.j.swift_at_gmail.com> wrote:
> Is there any reason why I shouldn't use my Windows system to place a
> working copy in a directory on our Linux server via a SAMBA share?
> My N:\ drive maps to the root of our server, so I could update the CGI
> scripts by placing a working copy in N:\var\apache2\www\cgi-bin\
Using network shares to host working copies is not officially supported. It
may work, it may not work, or it may work now and stop working later. You
are on your own.
The working copy should certainly NOT be accessed by SVN clients from
different operating systems (i.e. don't share a working copy between TSVN
and a Linux client.
I have all the necessary access permissions - I'm currently updating the
> scripts by editing them directly on the share.
> The scripts are not sensitive to Windows CRLF vs Linux LF line-ends.
> My ultimate goal would be to use a post-commit hook to do the work for me.
> I realise that I could try it and see what happens, but it might work at
> first, then develop problems later.
A more robust way of working is to use a Linux client to update the code on
the Linux server. If the server hosts the repository as well, you can use a
post-commit server hook to update the working copy. If the repository is
hosted elsewhere, you could either schedule a periodic 'svn update', or use
some other mechanism to trigger the update after a commit.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-06-02 03:18:32 CEST