Re: Multiple projects with Gitweb
- From
Drew Northup <drew.northup@maine.edu>
- Date
- Jul 13, 2011, 14:12 UTC
- Message-ID
- <1310566351.5205.9.camel@drew-northup.unet.maine.edu>
- In-Reply-To
- <700B9246C3446949B8085B181F2C217804E59B@renexmb01.roe2.renesasmobile.com>
On Wed, 2011-07-13 at 13:10 +0000, Mathieu.Pogeant@renesasmobile.com wrote:
Show 9 quoted lines
> Hello, > > I'm trying to have this with GitWeb. > I have a repo under /project1 and a repo under /project2 on my Git server. > I would like to access these 2 repo via Gitweb like that: http://mygitserver/project1 and http://mygitserver/project2. > The problem is that gitweb.conf permit to use just one repo with directive $projectroot. > > Did someone face the same problem? > If needed, I can share configuration file.
Mathieu, There is no requirement that gitweb only be provided by the HTTPd server once per machine or virtual host. It is entirely reasonable to set up two subdirectories (project1 and project2) in your virtual host's home and serve gitweb from each of those separately using an instance-local configuration file. That way each instance can be customized.
The /etc/gitweb.conf file is not meant to provide for that customization. The way that gitweb is currently constructed, if you use a local configuration file for an instance it will completely ignore the system-wide configuration file (I didn't make that decision, as it doesn't make much sense to me either), so you will have to make sure that ALL settings required are set in each instance-local configuration.
I plan on re-submitting my touch-ups to that documentation now that a have a minor window of sanity here at work (not that I expect that to last).
-- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59