Ask Your Question

Git and Gitolite to have GitWeb added for integration to a Mantis server via a plugin

asked 2013-09-16 10:21:41 -0500

cwbuege gravatar image

Hello all.

I'm trying to get a git server setup in the following configuration: Fedora 16 server (being dictated to me by others - they aren't (at this time) willing to go to a newer version of Fedora) 32-bit (but moving to 64-bit is acceptable) vProc (virtual machine), RAM, and HDD requirements are flexible so whatever is needed there

The git server (called is already hosting gitolite and that setup process is very well documented at this point. I'd like to add gitweb to the same server so that repos can be accessed, browsed, etc. from a web browser. I'm also looking to implement a plugin on a separate Mantis server so that the Mantis bug tracking can tie directly into the version control for resolution tracking.

The problem I'm running into is getting gitweb up and running on the git/gitolite server so that the repos can be seen. I'm currently unable to get the Apache instance to see the repos. I get very close, but can't just get it to work.

Does anyone know of any FAQs for what I'm trying to do? I've checked out several sites, with this one being the forerunner right now for what I'm trying to do: with a path of /quickly-setup-git-server-with-gitolite-gitweb-ssh-and-http-auth/

What I did just realize from this site is that the version of git that they are using (1.7.8) and the latest version of git under Fedora 16 (1.7.7) could be related to my issue.

Another thing I don't know is how the different versions of git will play with each other. I setup the gitolite-admin on a Red Hat 6.4 x64 system, where his version of git is showing up as 1.7.1 and another Fedora box, this one with v19, whose git version is 1.8.3. Am I just making things way difficult for myself? Is there a way to get all three of my test clients to the same version of git to get this working?

The next thing I'm gonna try to do is get a Fedora 19 git server up with gitweb and gitolite to see if that works for me.

If anyone has any recommendations for me, please feel free to point me in that direction because at this point I'm at a total loss.

Thanks, Charles

edit retag flag offensive close merge delete


Unless you get errors when pushing or pulling code, there shouldn't be an issue with having different versions of git.

hmaarrfk gravatar imagehmaarrfk ( 2013-09-16 11:58:06 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted

answered 2013-09-16 12:56:41 -0500

cwbuege gravatar image

Hmaarrfk -

I've already been playing around with those links. I found out that the plugin that we want to use has to be used via GitWeb, so that eliminates GitList.

The part of the instructions for GitWeb in the link you've given me that confuses me is the fact that the setup tells me to copy the repos into another directory. How will the copy that I made be updates whenever user check data into the repos? I'd think that this would just take a static 'picture' of the repository that then wouldn't change. How can I keep the information up to date? That's what I don't get about this.

Thanks, Charles

edit flag offensive delete link more


Please move this to a comment of my post... I'll edit my answer to address your question.

hmaarrfk gravatar imagehmaarrfk ( 2013-09-16 14:10:57 -0500 )edit

It won't let me. There's no 'post a comment' link under your comment below.

cwbuege gravatar imagecwbuege ( 2013-09-16 14:15:05 -0500 )edit

maybe you needed more karma. I just gave you some.

hmaarrfk gravatar imagehmaarrfk ( 2013-09-16 16:36:20 -0500 )edit

answered 2013-09-16 11:56:36 -0500

hmaarrfk gravatar image

updated 2013-09-16 14:17:09 -0500

I have a very similar setup on my computer. I probably won't be able to give you the full specs this week, but maybe this can help you get going.



I actually moved to nginx in F19 because I couldn't get SuExec working with Apache 2.4.

My tip would be to try to disable SELinux for a while, and see what SELinux warnings come up and follow the instructions to fix them. SELinux gave me some trouble initially but now I have SELinux enforced on my box.

---- Clarification ---- You said that they told you to copy your git repositories. I think GitWeb uses bare repositories. They just want all your repositories to be in the same directory. The other important thing is that the gitweb/apache user have read (maybe write too???) access to the repositories.

In your case, I'm assuming that gitolite already has all the repos in the directory /home/gitolite/repositories, so just point gitweb there in /etc/gitweb.conf file in the line $projectroot = '/home/gitolite/repositories';

edit flag offensive delete link more

Question Tools


Asked: 2013-09-16 10:21:41 -0500

Seen: 915 times

Last updated: Sep 16 '13