Simple steps to install configuration subversion under Windows

Source: Internet
Author: User
Tags rar svn update win32 tortoisesvn
Simple steps to install configuration subversion under Windows

[ installation Procedures and documentation instructions for use]

svn-1.4.0-setup.exe: Subversion service-side 1.4.0 installation program;

SubService.rar:SubServe services Windows accessibility tools;

Tortoisesvn-1.4.0.7501-win32-svn-1.4.0.msi: The recommended use of a Windows Explorer integrated client tool.

Instructions for using the TORTOISESVN-NIGHTLY-1.4.0-ZH-CN.CHM:TORTOISESVN client tool.

Svn-book-cn.pdf:subversion's Chinese version of the manual.

[ server-side installation configuration steps]

1. Use svn-1.4.0-setup.exe to install server-side programs;

2. Extract SubService.exe from Subservice.rar to [Subversion installation path]/bin directory;

3. Specifies the root directory of the SVN service version library (all subsequent version files will be stored in this directory):

A) Run cmd and enter the command line;

b execute the command and make a root directory, assuming that the directory you specify is: D:/svnvob:

svnservice-install-d-R d:/svnvob

4. Start the SVN service: Open Administrative Tools-services, locate the Svnservice service, set the startup type to Automatic, and start the service;

The server-side installation configuration is complete, and then the project version library is established.

[ server-side build version Library]

5. Create a temporary directory, and put all the project files into the directory, the general directory structure examples are as follows:

E:/temp ### You create a temporary directory, the version library can be deleted after the establishment.

├─myproject1 ### your first project directory.

├─branches ### Recommended Branch directory to build.

├─tags ### recommended for the establishment of the label directory.

└─trunk ### the required primary branch directory, and all initial versions of the project files are placed in the directory.

└─01doc ### below for your own project directory, as needed to create yourself.

└─02source

└─03release

└─ ...

└─myproject2 ### your second project directory.

├─branches

├─tags

└─trunk

└─ ...

└─ ... ### your other project directory.

6. Install the client program using Tortoisesvn-1.4.0.7501-win32-svn-1.4.0.msi;

7. To build a version library:

A If you create a project directory (such as MyProject1) under the root directory of your SVN service version library (such as the previous d:/svnvob), create a good path such as: D:/svnvob/myproject1

(b) In the Explorer, select the "MyProject1" directory, right-click the "TortoiseSVN"-"Create Repository Here" submenu to create a version library;

Note: The MyProject1 directory must be empty or you cannot create a success.

c If the creation is successful, MyProject1 directories and Readme and format files are automatically created in the CONF,DAV,DB directory:

8. To import temporary files into an established version library:

(a) In the Explorer, select the 5th step of the Temporary project directory "MyProject1" (such as the former E:/temp/myproject1), right-click the "TortoiseSVN"-"Import" submenu;

b In the Import dialog box that pops up, select the URL as "svn://[Server IP Address]/myproject1" and click "OK", and then the file and directory information will be displayed in the following dialog box, and the last one shows "Completed at Version 1 ”。

9. To configure a version library:

(a) Locate the D:/SVNVOB/MYPROJECT1/CONFG directory and make the relevant configuration;

(b) First edit the svnserve.conf file (if you are using http:and/or file:urls, you do not need to modify the file): The key is three lines:

Line 12: Remove the comment and modify it to below write, indicating that anonymous access is not allowed

Anon-access = None

Line 13: Remove the annotation and modify it to below write to allow authorized write access

auth-access = Write

Line 18: Remove the annotation and modify it to below write, indicating that the user name and password are set using the passwd configuration file.

Password-db = passwd

Line 25: Remove the annotation and modify it to below write, which means that the Authz configuration file is used to set permissions group management.

Authz-db = Authz

c) Edit passwd file, configure username and password, such as:

[Users]

SA = admin

AAA = AAA

bbb= BBB

D Edit the Authz file and configure permissions groupings, such as:

[Groups]

Manager = sa

Developer = aaa,bbb

[/]

@manager = RW

AAA = RW

BBB = R

[/:01doc]

@manager = RW

AAA = RW

BBB = R

...

10. Test version Library for checkout operations:

(a) In Explorer, select your own working directory, such as "E:/myproject1", and right-click the "Svn CheckOut" menu;

B In the Pop-up Checkout dialog box, select the URL is "svn://[Server IP Address]/myproject1", and then click OK; The following dialog box will display the file and directory information added to the list, the last one to show "Completed at Version 1 ”。

If you can checkout, the entire library configuration is complete.

The previous steps are to configure and test the client action on the server. See below for checkout, commit, and update operations on another machine.

[ Client Installation configuration steps]

1. Install the client program using Tortoisesvn-1.4.0.7501-win32-svn-1.4.0.msi;

2. In the Explorer, select your own working directory, such as "E:/myproject1", and right-click the "Svn CheckOut" menu;

3. In the Pop-up Checkout dialog box, select the URL as "svn://[Server IP address]/myproject1";

4. Enter the username and password for the server configuration in the prompt username and Password dialog box, then click OK, and then the file and directory information will be displayed in the following dialog box, and the last one shows "Completed at Version 1".

If successful, you can see the corresponding code file in the local E:/myproject1 directory. Select files or directories to perform SVN update (updated from server) and SVN commit (commit changes to the server).

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.