The main question is: is a subversion server necessary in this scenario?

Question

Right now:

• I have several personal software projects that I develop (only me, and only on one PC).
• make extensive use of TortoiseSVN for version control
• run CollabNet Subversion Server on one PC

Are there any advantages to having a server instead of just pointing to the repository directory?

For example: instead of assigning a value svn://localhost/projectname, I could just pass on C:/development/projectnameand leave with it.

Can anyone advise me what is the best practice in this senario?

Answer 1

, Subversion. TortoiseSVN ( file://), .

, :

• Subversion .
• .
• - .

Answer 2

, - , . , . , - .

Answer 3

, /. Windows 2008, Subversion Tortoise .

, . , , .

Answer 4

, , Mercurial DVCS.

Answer 5

. , ://url.

, URL- file:// , / . , .

- , ( svnserve ).

Answer 6

, . ?

100% . ?

, . .

CollabNet Windows . .

, . , , , .

. , .

Answer 7

Although I would recommend DVCS like git or Mercurial, I always used a server. Thus, I could access my repository from my computer at school, as well as from the desktop on which the repository was located.

Answer 8

Personally, I use Mercurial and free bitback hosting. I do not feel very confident if the data exists in only one place.

(Just a mention of Mercurial, as they offer free private hosting to work without opening)