Skip to content
This repository has been archived by the owner. It is now read-only.
Implementation of git-http-backend for IIS7/ASP.NET
Branch: master
Clone or download
Latest commit 389824f Feb 27, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
GitAspx.Tests Upgrade to mvc3 Jan 25, 2011
GitAspx Explicitly reference 1.0.0.0 of System.Web.WebPages and System.Web.He… Jan 6, 2013
lib Missing reference for SharpZipLib Apr 9, 2011
.gitignore Re-add ignore/readme with correct line endings Jun 21, 2010
Build.bat Build script Jul 4, 2010
Build.boo Include test target in build script Oct 20, 2010
GitAspx.5.1.ReSharper Fix some tests Jun 26, 2010
GitAspx.sln Add test project Jun 22, 2010
License.txt
README.txt Update README.txt Feb 27, 2018

README.txt

This is a simple implementation of git-http-backend written in ASP.NET that can be used to read/write git repositories on Windows with IIS.

** This was an experimental project that is no longer maintained, developed or supported. Please feel free to use the code but no further changes will be made and pull requests will not be merged in **

Inspired by Grack (http://github.com/schacon/grack)

This is largely untested, but has been developed with IIS7.5 under Windows 7 x64. 

The version of GitSharp included is a custom build with some minor changes. Details to follow.

Requirements:
- VS2010 with .NET 4
- ASP.NET MVC2
- IIS7+

Edit the web.config and change the "RepositoriesDirectory" app-setting to point to a directory containing git repositories.

Assuming that your repositories directory looks like this:

C:\Repositories\Repo1.git

...and the RepositoriesDirectory app-setting is configured to be C:\Repositories:

<appSettings>
		<add key="RepositoriesDirectory" value="C:\Repositories"/>
</appSettings>
	
...and the application is configured under IIS7 on port 8000, then issuing the following command will cone the Repo1.git repository:

git clone http://localhost:8000/Repo1.git

Once cloned, push/pull work as expected.

There are currently no tests (something I hope to rectify soon). If you run into a problem, the best way to troubleshoot is by using Fiddler to see the raw request/response data.
You can’t perform that action at this time.