SVN installation configuration details

Reproduced http://www.cnblogs.com/seiitsu/archive/2013/01/14/2859137.html

This is what I recorded when installing and configuring SVN ..... Today we will share it with you .... Hope to help you a little ......

I. Preparations

 

).

Ii. server and client Installation

3. Create a version Library (Pro1)

To run the Subversion server, you must first create a version Library (pro1 ). The version library can be seen as a place where data is centrally stored and managed on servers.

Create a version library. Create an empty D: \ SVN folder as the root directory of all version libraries. Then, go to the command line and switch to the bin directory of subversion. Run the following command:

Svnadmin create d: \ SVN \ pro1

This command creates a version library pro1 under D: \ SVN. Under pro1, some folders and files are automatically generated.

We can also use tortoisesvn to perform this step graphically:

First create an empty Directory D: \ SVN \ pro1, note that it must be empty. Right-click the pro1 folder and choose tortoisesvn> Create repository here ...", Then you can select the version library mode. Here you can use the default fsfs, and then create a series of folders and files, which are the same as those created on the command line.

4. Run an independent server

At this time, the Subversion service has not started yet, but the version library has been created through its command. Enter the following in the Command window:

Svnserve.exe-daemon

Svnserve will wait for the request on port 3690, and the-daemon (two dashes) Option tells svnserve to run in daemon mode, so that it will not exit before manual termination. Do not close the command line window. Close the window will stop svnserve.

To verify that svnserve works properly, use tortoisesvn-> repo-browser to view the version library. In the pop-up URL dialog box, enter:

SVN: // localhost/SVN/pro1

Click OK to view the directory tree structure of the pro1 version library, but pro1 is an empty database.

You can also use the-root option to set the root location to restrict the access directory of the server, so as to increase security and save time for inputting the svnserve URL:

Svnserve.exe-Daemon-root drive: \ path \ To \ Repository

In the previous test, svnserve runs as follows:

Svnserve-D-r d: \ SVN \ pro1

Then the browser URL in tortoisesvn is reduced:

SVN: // localhost/pro1

5. Configure users and permissions1, ModifySvnserveFile

Open the D: \ SVN \ pro1 \ conf directory in the text editor and modify svnserve. conf:

Set: # password-DB = passwd

Change to: Password-DB = passwd // verify the file passwd used by the user

Remove the # annotator. Note that there is no space before it.

Set: # anon-access = read

Change to: Anon-access = NONE // users who fail to pass the verification do not have operation Permissions

Set: # auth-access = write

Change to auth-access = write // only authenticated users can have read and write permissions.

Set: # authz-DB = authz

Change to: authz-DB = authz // verify the file used by the user.

 

2, ModifyPasswdFile

Then modify the passwd file in the same directory and add an account:

Set:

[Users]
# Harry = harryssecret
# Sally = sallyssecret

Add an account:

[Users]
# Harry = harryssecret
# Sally = sallyssecret
Admin = Admin

3, ModifyAuthzFile

Modify the authz file in the same directory to set the access permission.

Create a user group under groups. For example, here is:

[Groups]

Admin = Admin

Developer = Workshop 1, workshop 2

Qatester = test

The preceding three user groups are created: Admin, developer, qatester, and other corresponding group members.

Set the access path

[Version Library :/]

* = R

@ Admin = RW

As shown above, all users can read files in the entire SVN directory, and the Admin group has read and write permissions ("*" indicates all users, r indicates read, and W indicates write)

You can set the access permissions for specific version libraries:

[Version Library :/]

@ Developer = RW

The preceding settings indicate that all the members of the developer group have the read and write permissions for all the files under version library D.

Vi. initialize Import

The following describes how to import our data (project) to this version library and manage our data in the future. Any of our changes are recorded by the version library. Even if we lose or correct the data, the version library can help us retrieve the data.

For example, I have
The test folder contains some test documents. In this folder, "right-click-> tortoisesvn->
Import ..." In the "URL
Input "SVN: // localhost/pro1" in repository ". After clicking OK, enter the account. Enter test in both the user name and password. Complete
Then all the content in the guestbook is imported to SVN: // localhost/SVN/pro1/CS.

VII. Basic operation procedure1, Retrieve (Check out)

Extract the version library to a working copy:

To any empty directory, such as creating an empty folder F: \ work in partition F. "Right click-> SVN
Checkout ". In the URL
Input "SVN: // localhost/SVN/pro1/CS" in repository to get a working copy of the content in CS.

2, Save (Check in)/Submit (Commit)

Make changes in the work copy and submit:

Open a file in the CS work copy, modify it, and then "right-click-> SVN commit... ". In this way, the modifications are submitted to the version library, which stores the submitted data as needed.

Right-click the modified file and choose tortoisesvn> show
Log, you can see all the submissions to this file. Right-click different revision entries and choose "compare with working ".
Copy, we can compare the differences between the files that work copies and the selected revision version.

Fixed Link: http://www.test-life.org /? P = 82 | test path-my test Space

This is what I recorded when installing and configuring SVN ..... Today we will share it with you .... Hope to help you a little ......

I. Preparations

 

).

Ii. server and client Installation

3. Create a version Library (Pro1)

To run the Subversion server, you must first create a version Library (pro1 ). The version library can be seen as a place where data is centrally stored and managed on servers.

Create a version library. Create an empty D: \ SVN folder as the root directory of all version libraries. Then, go to the command line and switch to the bin directory of subversion. Run the following command:

Svnadmin create d: \ SVN \ pro1

This command creates a version library pro1 under D: \ SVN. Under pro1, some folders and files are automatically generated.

We can also use tortoisesvn to perform this step graphically:

First create an empty Directory D: \ SVN \ pro1, note that it must be empty. Right-click the pro1 folder and choose tortoisesvn> Create repository here ...", Then you can select the version library mode. Here you can use the default fsfs, and then create a series of folders and files, which are the same as those created on the command line.

4. Run an independent server

At this time, the Subversion service has not started yet, but the version library has been created through its command. Enter the following in the Command window:

Svnserve.exe-daemon

Svnserve will wait for the request on port 3690, and the-daemon (two dashes) Option tells svnserve to run in daemon mode, so that it will not exit before manual termination. Do not close the command line window. Close the window will stop svnserve.

To verify that svnserve works properly, use tortoisesvn-> repo-browser to view the version library. In the pop-up URL dialog box, enter:

SVN: // localhost/SVN/pro1

Click OK to view the directory tree structure of the pro1 version library, but pro1 is an empty database.

You can also use the-root option to set the root location to restrict the access directory of the server, so as to increase security and save time for inputting the svnserve URL:

Svnserve.exe-Daemon-root drive: \ path \ To \ Repository

In the previous test, svnserve runs as follows:

Svnserve-D-r d: \ SVN \ pro1

Then the browser URL in tortoisesvn is reduced:

SVN: // localhost/pro1

5. Configure users and permissions1, ModifySvnserveFile

Open the D: \ SVN \ pro1 \ conf directory in the text editor and modify svnserve. conf:

Set: # password-DB = passwd

Change to: Password-DB = passwd // verify the file passwd used by the user

Remove the # annotator. Note that there is no space before it.

Set: # anon-access = read

Change to: Anon-access = NONE // users who fail to pass the verification do not have operation Permissions

Set: # auth-access = write

Change to auth-access = write // only authenticated users can have read and write permissions.

Set: # authz-DB = authz

Change to: authz-DB = authz // verify the file used by the user.

 

2, ModifyPasswdFile

Then modify the passwd file in the same directory and add an account:

Set:

[Users]
# Harry = harryssecret
# Sally = sallyssecret

Add an account:

[Users]
# Harry = harryssecret
# Sally = sallyssecret
Admin = Admin

3, ModifyAuthzFile

Modify the authz file in the same directory to set the access permission.

Create a user group under groups. For example, here is:

[Groups]

Admin = Admin

Developer = Workshop 1, workshop 2

Qatester = test

The preceding three user groups are created: Admin, developer, qatester, and other corresponding group members.

Set the access path

[Version Library :/]

* = R

@ Admin = RW

As shown above, all users can read files in the entire SVN directory, and the Admin group has read and write permissions ("*" indicates all users, r indicates read, and W indicates write)

You can set the access permissions for specific version libraries:

[Version Library :/]

@ Developer = RW

The preceding settings indicate that all the members of the developer group have the read and write permissions for all the files under version library D.

Vi. initialize Import

The following describes how to import our data (project) to this version library and manage our data in the future. Any of our changes are recorded by the version library. Even if we lose or correct the data, the version library can help us retrieve the data.

For example, I have
The test folder contains some test documents. In this folder, "right-click-> tortoisesvn->
Import ..." In the "URL
Input "SVN: // localhost/pro1" in repository ". After clicking OK, enter the account. Enter test in both the user name and password. Complete
Then all the content in the guestbook is imported to SVN: // localhost/SVN/pro1/CS.

VII. Basic operation procedure1, Retrieve (Check out)

Extract the version library to a working copy:

To any empty directory, such as creating an empty folder F: \ work in partition F. "Right click-> SVN
Checkout ". In the URL
Input "SVN: // localhost/SVN/pro1/CS" in repository to get a working copy of the content in CS.

2, Save (Check in)/Submit (Commit)

Make changes in the work copy and submit:

Open a file in the CS work copy, modify it, and then "right-click-> SVN commit... ". In this way, the modifications are submitted to the version library, which stores the submitted data as needed.

Right-click the modified file and choose tortoisesvn> show
Log, you can see all the submissions to this file. Right-click different revision entries and choose "compare with working ".
Copy, we can compare the differences between the files that work copies and the selected revision version.

Fixed Link: http://www.test-life.org /? P = 82 | test path-my test Space