Build a GIT Server on Windows Server 2008 R2

Bonobo Git Server is an open source GIT source code Server running on IIS6/7, MVC 3, and. net 4.0 platforms. The following describes how to install Windows Server 2008 R2:

1. Prepare the environment

MsysGit

TortoiseGIT

Install IIS 2008 on Windows Server 7.5 R2

Microsoft. NET Framework 4.0

ASP. net mvc 3

2. Download the Bonobo Git Server installation package and decompress it.

3. Download the 64-bit version of System. Data. SQLite to replace the dll file with the same name in the/bin/directory.

4. Copy the entire directory after extracting and replacing the dll file to the target path, but it is the default c: inetpubwwwroot Directory. You can also configure a git subdomain name separately, here I select the latter. Note: ASP should be selected for the application pool. NET v4.0

5. Set the App_Data directory permission to "full control". Right-click the directory and choose> Properties> Security> Edit

 

6. Open the browser and enter http: // localhost/Bonobo. git. server or a sub-domain added in step 5 (such as http://git.chiefleo.me/), log on as the default Administrator: user name-admin, password-admin

7. Specify the root directory of the code library in "Global Settings" and set the file system permissions for this directory (write permission is required)

8. Create a code library: Repositories-> Create New Repository-> enter information about the code library-> after creation, click the code library name, you can see the corresponding Git Repository Location. In the future, you can use this link to clone, pull, and push the code ~

GIT usage problem summary:

1. After bonobo git server is installed, access through http: // localhost/Bonobo. Git. Server or subdomain name. The page is blank.

Solution: refer to Step 5 above to set the App_Data directory permission to "full control"

2. When GIT pushes large files, an error message is displayed:

Pushing to http://git.chiefleo.me/Git.aspx/xxx
Fatal: protocol error: bad line length character: <! DO
Fatal: The remote end hung up unexpectedly
Error: RPC failed; result = 55, HTTP code = 200

Solution: open web. in <system. for web> nodes, set the maximum request length (maxRequestLength) to 102400000. under webServer> node, set the maximum allowed content length (maxAllowedContentLength) to 102400000. The related code is as follows:

The code is as follows:	Copy code
<System. web> <HttpRuntime maxRequestLength = "102400000"/> ... </System. web> <System. webServer> ... <Security> <RequestFiltering> <RequestLimits maxAllowedContentLength = "102400000" type = "codeph" text = "/codeph"/> </RequestFiltering> </Security> </System. webServer>