LAVA: TortoiseSVN setup question - LAVA

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

TortoiseSVN setup question Rate Topic: -----

#-19 User is offline   george seifert 

  • Extremely Active
  • PipPipPipPip
  • Group: Members
  • Posts: 349
  • Joined: 19-August 05

Posted 03 June 2010 - 01:27 PM

We're a relatively small development group. There will probably be at most 3 people (but usually just me) accessing the code. Do you know if it's necessary to have a special server or could we just have the repository on a network drive? If we do set it up that way at first would it be hard to migrate to a server later if necessary?

George

0

#-18 User is offline   mike5 

  • Very Active
  • PipPipPip
  • Group: Members
  • Posts: 64
  • Joined: 02-March 10
  • Location:Slovenia
  • Version:LabVIEW 2009
  • Since:2009

Posted 03 June 2010 - 01:34 PM

View Postgeorge seifert, on 03 June 2010 - 01:27 PM, said:

We're a relatively small development group. There will probably be at most 3 people (but usually just me) accessing the code. Do you know if it's necessary to have a special server or could we just have the repository on a network drive? If we do set it up that way at first would it be hard to migrate to a server later if necessary?

George



It's a Subversion question, but anyway... As soon as you have more than one developer you need to access repository through a server. Otherwise you're just begging for repository corruption.

Br, Mike
0

#-17 User is offline   Biometrology 

  • 2 more posts to go.
  • Group: Members
  • Posts: 8
  • Joined: 27-February 08

Posted 03 June 2010 - 02:53 PM

View Postgeorge seifert, on 03 June 2010 - 01:27 PM, said:

We're a relatively small development group. There will probably be at most 3 people (but usually just me) accessing the code. Do you know if it's necessary to have a special server or could we just have the repository on a network drive? If we do set it up that way at first would it be hard to migrate to a server later if necessary?


George, you could do this (I did) - but I wouldn't necessarily recommend it.
One of the problems of keeping the repository on a network drive is that any random person can accidentally move, delete or rename the path to them.Posted Image

To move from the shared drive to a server I had to do the following steps (from memory):
Posted Imageexport the repository using Subversion (I had to install it just to do this).
Posted ImageThe very large file resulting then had to be imported into the new repository on the server by one of our IT guys
Posted Image All the working copies then have to be changed to point at the new repositories (using the relocate command)
Posted Image This only works if the repository has not changed since you exported it!!!!

Hope this guides your decision.... Posted Image

Alex
0

#-16 User is offline   george seifert 

  • Extremely Active
  • PipPipPipPip
  • Group: Members
  • Posts: 349
  • Joined: 19-August 05

Posted 03 June 2010 - 03:15 PM

Thanks guys. Sounds like I better get IT involved from the get go.

Sorry I knew it was a Subversion question (I am using it for LV though), but I knew how helpful everyone is anyway.
George
0

#-15 User is offline   Shaun Hayward 

  • Very Active
  • PipPipPip
  • Group: Members
  • Posts: 123
  • Joined: 22-October 07
  • Location:Fort Lee, NJ, USA
  • Version:LabVIEW 2009
  • Since:2003

Posted 03 June 2010 - 03:47 PM

View Postgeorge seifert, on 03 June 2010 - 03:15 PM, said:

Thanks guys. Sounds like I better get IT involved from the get go.

Sorry I knew it was a Subversion question (I am using it for LV though), but I knew how helpful everyone is anyway.
George


There's a great free (although it also has a paid "pro" version) subversion server called VisualSVN Server (http://visualsvn.net/server/) - it is super easy to modify repositories, etc and even plays nicely with Active Directory if your on a Windows Domain setup.

Shaun
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic