Placing a working copy on a network drive

[Steve Swift]

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\

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.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2967597

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Gerald Britton]

IIRC SVN assumes it has sole control over the WC. In the case of a network share, that may not be true. That is, someone else (even you!) could access the share from another session. This could lead to WC corruption -- not a big issue if you do regular commits, I suppose.

I usually discourage my team from going that route. There is another factor that is more important for them, though: performance when working remote. I believe that SVN thinks that it is working off a local WC and takes no special steps to optimize for a (possibly very) remote WC.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2967615

[Gabri Nurtinaz Shally]

On Jun 1, 2012 8:33 PM, "Gerald Britton" <gerald....@gmail.com> wrote:
>
> I usually discourage my team from going that route.  There is another factor that is more important for them, though: performance when working remote.  I believe that SVN thinks that it is working off a local WC and takes no special steps to optimize for a (possibly very) remote WC.
>

i've read in this mailing list, that someone get caught in a long process of commit/update, because his wc is placed in a shared folder. so it is not encouraged to put wc in a shared folder.

[Bob Archer]

> 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\
>
> 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.

There are several issues with having your working copy on a share, especially a samba share.

Will it actually be used as a working copy? Or, do you just want the code to be on the server so people/server can access it?

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2967778

[Markus Schaber]

Hi, Steve,

Von: Steve Swift [mailto:steve....@gmail.com]
> 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?

There are some issues, the main one is that some network file systems or setups do not provide clean locking semantics.

Other possible issues include line ending conversion, character set differences, and case differences.

> 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\
>
> 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.

So the line ending conversions are not an issue for you, it seems.

> My ultimate goal would be to use a post-commit hook to do the work for me.

Yes, but that hook should run directly on the server.

> I realise that I could try it and see what happens, but it might work at
> first, then develop problems later.

Maybe you can create a batch file which uses "plink" or a similar tool to log onto the server and run "svn update" there.


Best regards

Markus Schaber
--
___________________________
We software Automation.

3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50

Email: m.sc...@3s-software.com | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects

Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2967915

[Gabri Nurtinaz Shally]

On May 31, 2012 5:03 PM, "Steve Swift" <steve....@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\
>
> 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.
>

i think it is ok to put WC on a network drive as long as only one user using it. so, in your case, it is not a problem.

but, there is another solution. add a cron job to update thus WC so you don't have to update it manually.

[Andy Levy]

On Thu, May 31, 2012 at 6:03 AM, Steve Swift <steve....@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\
>
> 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.

You'll take a considerable performance hit, icon overlays may get
wonky, your Samba setup may not have locking configured properly to
handle the SQLite database the WC uses, and if you're working in a
group, it's a completely bad idea.

Use the hook or a CI system to push your updates to the server.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2968134

[David Balažic]

Steve Swift 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?

If I remember correctly placing working copies on network shares is not recommemded,
but I just checked the FAQ and the only related entry is http://tortoisesvn.net/faq.html#ovlonlylocal :

Why are the icons only visible on local and not on network drives?

Go to the Settings -> Look and Feel -> Icon Overlays and check the drive types for which you want to see overlay icons. Be aware that enabling overlays for network drives will slow down not only TortoiseSVN but the whole system.


Regards,
David

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2968312

[Jean-Marc van Leerdam]

Hi,

On 31 May 2012 12:03, Steve Swift <steve....@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.

 

--
Regards,

Jean-Marc