Geek asks and answers

First base walkthrough with TortoiseSVN

Well, I was convinced that SVN was the path to the previous post , but I have not yet seen the insight. I am not sure how to install SubVersion for my development environment.

Here is my current setup. I am not going to get involved in this, and it would be very nice if subversion could sit next to him:

Job:

N: \ Projects
N: \ Projects \ Lib
N: \ Projects \ App1
N: \ Projects \ App1 \ Help
N: \ Projects \ App1 \ Images
N: \ Projects \ App2
..etc

N: located on a separate server in the building.

There are several other development machines with locally installed tools, but all development takes place referring to files on the server - that is, the source code is not stored on workstations.

home

A laptop with the same set of development tools and sources in c: \ Projects \ App1 .. etc., i.e. configuration mirror on n: \ Projects at work.

Sources between N: \ Projects and C: \ Project are currently supported by the custom application along with DropBox. File exceptions ensure that non-source files are not synchronized

I want to run SubVersion with this setting.

  • Where can I host the repository?
  • Assuming I can keep the repository in a mutually accessible place, will SVN remove the current need for synchronization between work and home?
+3
5

- () Subversion , , . , , . , . - . , :

http://www.projectlocker.com/

. Delphi ( → delphi), , , . subversion (, , ) , , .

(a) SVN, (b) SVN- Rad Studio XE, Rad Studio XE (c) , JCL, Rad Studio XE.

, , - , , , . . .

, svn co http://reposite.something.com/svn/myproject, , . , , GUI - . , .

subversion, , , . , , - . sourceforge. (a) (b) , .

, , subversion, ( LAN), VPN .

+4

Subversion, Subversion, . ( , ).

N:\Projects . Subversion , . , . , "" Subversion - .

+8

1: , . , , ​​ Mercurial Git

2: , . , . SVN .

+3
  • , SVN.
  • , SVN , .
  • Commit/Update , , .

, ( , , ), . IP- IP- .

, , , "", , "" ( - "" DVCS, , ).

. Git Mercurial DVCS (Git , ).

+1
  • . ( ..), , . VCS, , . / . , , , , SMB - , , . , IMHO, sanbox, .
  • If you can access the SVN server from home (i.e. through a VPN), it will not be different from working in the office. You will "synchronize" (update / commit) your sandbox of your laptop in the same way, you do not need a local server and repository. If you need a local server (the reason may be, you cannot access the central repository from the outside, version files that are disabled should work, etc.), There may be replication methods on SVN servers, but at this point perhaps distributed VCS should work better in such a scenario.
+1
source

More articles:


All Articles