Comments on: git on shared hosting with git-http-backend http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/ blog about being mobile, but including technology Mon, 21 May 2012 06:05:22 +0000 http://wordpress.org/?v=2.5.1 By: santos http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-34596 santos Thu, 14 Jul 2011 11:54:31 +0000 http://www.mobiphil.com/?p=180#comment-34596 Hello, I didn't understand why the RewriteRule uses this path: /git/git-http-backend.sh/$1 Will git-http-backend.sh be executed? I known the directive RewriteMap scripts execution. Hello,

I didn’t understand why the RewriteRule uses this path: /git/git-http-backend.sh/$1

Will git-http-backend.sh be executed?
I known the directive RewriteMap scripts execution.

]]> By: valhallasw http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-16030 valhallasw Tue, 12 Oct 2010 22:20:31 +0000 http://www.mobiphil.com/?p=180#comment-16030 Hi Tom, After a lot of work, I found the cause for the code-22 error. If git-http-backend does not consider you authenticated, git push will fall back to webdav, which causes all kinds of trouble. The solution, in my case, was defining REMOTE_USER from REDIRECT_REMOTE_USER. For my setup, please see http://blog.procrastination.nl/2010/10/git-http-backend-on-shared-hosting-with.html Hi Tom,

After a lot of work, I found the cause for the code-22 error. If git-http-backend does not consider you authenticated, git push will fall back to webdav, which causes all kinds of trouble. The solution, in my case, was defining REMOTE_USER from REDIRECT_REMOTE_USER.

For my setup, please see http://blog.procrastination.nl/2010/10/git-http-backend-on-shared-hosting-with.html

]]> By: ianc http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-15438 ianc Fri, 17 Sep 2010 17:57:15 +0000 http://www.mobiphil.com/?p=180#comment-15438 This has been a very helpful tutorial. I'm having the same issues as tom, although my git-daemon-export-ok files is there. I'm a bit confused about website.com and the location of git projects. My public_html doesn't have a website.com folder, so I thought I'd try to put it directly in public_html/git. I've tried both (public_html/website.com/git and public_html/git) and experience problems with both. I found the regular expression used in RewriteRule won't match git projects with hyphens in their name. Changing it to [CODE] RewriteRule ^([a-zA-Z0-9._-]*\.git/(HEAD|info/refs|objects/(info/[^/]+|[0-9a-f]{2}/[0-9a-f]{38}|pack/pack-[0-9a-f]{40}\.(pack|idx))|git-(upload|receive)-pack))$ /git/git-http-backend.sh/$1[/CODE] This stopped the "not found: did you run git update-server-info" problems, but now I'm getting "error: The requested URL returned error: 500 while accessing http://somedomain.com/git/project.git/info/refs while cloning. Thoughts? And perhaps an explanation of whether website.com is necessary? I'm assuming it simply fits convention, perhaps when multiple domains are hosted by the same account. Also, I noticed tom said he put git-daemon-export-ok in /website.com/git/myproject.git. It should go in $HOME/gitprojects/myproject.git, right? The git project doesn't need to be copied into public_html? This has been a very helpful tutorial. I’m having the same issues as tom, although my git-daemon-export-ok files is there. I’m a bit confused about website.com and the location of git projects.

My public_html doesn’t have a website.com folder, so I thought I’d try to put it directly in public_html/git. I’ve tried both (public_html/website.com/git and public_html/git) and experience problems with both.

I found the regular expression used in RewriteRule won’t match git projects with hyphens in their name. Changing it to

[CODE]
RewriteRule ^([a-zA-Z0-9._-]*\.git/(HEAD|info/refs|objects/(info/[^/]+|[0-9a-f]{2}/[0-9a-f]{38}|pack/pack-[0-9a-f]{40}\.(pack|idx))|git-(upload|receive)-pack))$ /git/git-http-backend.sh/$1[/CODE]

This stopped the “not found: did you run git update-server-info” problems, but now I’m getting “error: The requested URL returned error: 500 while accessing http://somedomain.com/git/project.git/info/refs while cloning.

Thoughts? And perhaps an explanation of whether website.com is necessary? I’m assuming it simply fits convention, perhaps when multiple domains are hosted by the same account.

Also, I noticed tom said he put git-daemon-export-ok in /website.com/git/myproject.git. It should go in $HOME/gitprojects/myproject.git, right? The git project doesn’t need to be copied into public_html?

]]> By: mobiphil http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-11347 mobiphil Thu, 17 Jun 2010 21:56:21 +0000 http://www.mobiphil.com/?p=180#comment-11347 Tom: I added some time later a new git repo... I had the same error. The I remembered that I have to add the git-daemon-export-ok file. The I came here to update the instruction and to tell you what you should take care.. but I see that this solved your problem already. Tom:

I added some time later a new git repo… I had the same error. The I remembered that I have to add the git-daemon-export-ok file. The I came here to update the instruction and to tell you what you should take care.. but I see that this solved your problem already.

]]> By: Trac and git-http-backend « XRunHProf http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-11018 Trac and git-http-backend « XRunHProf Tue, 01 Jun 2010 12:09:10 +0000 http://www.mobiphil.com/?p=180#comment-11018 [...] http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend (for the idea of the cgi... [...] [...] http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend (for the idea of the cgi… [...]

]]> By: Tom Elam http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-10824 Tom Elam Thu, 20 May 2010 17:42:04 +0000 http://www.mobiphil.com/?p=180#comment-10824 mobiphil, Got clone to work. Should have paid more attention to the git-http-backend man page. I added the file git-daemon-export-ok to /website.com/git/myproject.git and all went well. Now I'm working on getting push to work. I'm cd'ing into the cloned repository, making and committing a change, and running the command: git push http://tomelam:password@onthesamepage.org/website.com/git/myproject.git and getting return code 22, 'fatal: git-http-push failed'. Tom mobiphil,

Got clone to work. Should have paid more attention to the git-http-backend man page. I added the file git-daemon-export-ok to /website.com/git/myproject.git and all went well.

Now I’m working on getting push to work. I’m cd’ing into the cloned repository, making and committing a change, and running the command:
git push http://tomelam:password@onthesamepage.org/website.com/git/myproject.git

and getting return code 22, ‘fatal: git-http-push failed’.

Tom

]]> By: mobiphil http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-10560 mobiphil Mon, 10 May 2010 21:40:58 +0000 http://www.mobiphil.com/?p=180#comment-10560 1. the "did you run git update-server-info" is a misleading error in this case, and in several other situations. The git guys should remove that 2. if the git-http-backend.sh is called, then it means that the real git-http-backend is not finding your project file, so you need to check if GIT_PROJECT_ROOT points to the right directory in the shell script 1. the “did you run git update-server-info” is a misleading error in this case, and in several other situations. The git guys should remove that
2. if the git-http-backend.sh is called, then it means that the real git-http-backend is not finding your project file, so you need to check if GIT_PROJECT_ROOT points to the right directory in the shell script

]]> By: Tom Elam http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-10557 Tom Elam Mon, 10 May 2010 20:07:02 +0000 http://www.mobiphil.com/?p=180#comment-10557 mobiphil, I just upgraded git on the server and client to 1.7.1 from 1.7.0, but the symptoms are unchanged. mobiphil,

I just upgraded git on the server and client to 1.7.1 from 1.7.0, but the symptoms are unchanged.

]]> By: mobiphil http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-10510 mobiphil Sun, 09 May 2010 11:29:47 +0000 http://www.mobiphil.com/?p=180#comment-10510 Tom: are you sure that you are on the latest git version both on the server and client? Tom:

are you sure that you are on the latest git version both on the server and client?

]]> By: Tom Elam http://www.mobiphil.com/2010/03/git-on-shared-hosting-with-git-http-backend/#comment-10492 Tom Elam Sat, 08 May 2010 18:49:43 +0000 http://www.mobiphil.com/?p=180#comment-10492 I noticed that git is not referring to a URL with the proper .htaccess, so I inserted 'website.com' in the URL passed to the git command. I also noticed that my HTTP GET request wasn't being authenticated, so I tried the command 'git clone http://tomelam:passwordxxx@onthesame.org/website.com/git/myproject.git'. Now I'm getting the error 'fatal: http://tomelam:bmc4387@onthesamepage.org/website.com/git/myproject.git/info/refs not found: did you run git update-server-info on the server?' and WireShark captures the HTTP exchange: GET /website.com/git/myproject.git/info/refs?service=git-upload-pack HTTP/1.1 HTTP/1.1 401 Authorization Required (text/html) GET /website.com/git/myproject.git/info/refs?service=git-upload-pack HTTP/1.1 HTTP/1.1 404 Not Found GET /website.com/git/myproject.git/info/refs HTTP/1.1 HTTP/1.1 404 Not Found I expected the GET request for /website.com/git/myproject.git/info/refs?service=git-upload-pack to be rewritten as a request for /git/git-http-backend.sh, and apparently it is, because I uncommented the logging in git-http-backend.sh and the following lines get printed to ~/logs/log: service=git-upload-pack GET /myproject.git/info/refs GET /myproject.git/info/refs I noticed that git is not referring to a URL with the proper .htaccess, so I inserted ‘website.com’ in the URL passed to the git command.

I also noticed that my HTTP GET request wasn’t being authenticated, so I tried the command ‘git clone http://tomelam:passwordxxx@onthesame.org/website.com/git/myproject.git‘. Now I’m getting the error ‘fatal: http://tomelam:bmc4387@onthesamepage.org/website.com/git/myproject.git/info/refs not found: did you run git update-server-info on the server?’ and WireShark captures the HTTP exchange:

GET /website.com/git/myproject.git/info/refs?service=git-upload-pack HTTP/1.1
HTTP/1.1 401 Authorization Required (text/html)
GET /website.com/git/myproject.git/info/refs?service=git-upload-pack HTTP/1.1
HTTP/1.1 404 Not Found
GET /website.com/git/myproject.git/info/refs HTTP/1.1
HTTP/1.1 404 Not Found

I expected the GET request for /website.com/git/myproject.git/info/refs?service=git-upload-pack to be rewritten as a request for /git/git-http-backend.sh, and apparently it is, because I uncommented the logging in git-http-backend.sh and the following lines get printed to ~/logs/log:

service=git-upload-pack GET /myproject.git/info/refs
GET /myproject.git/info/refs

]]>