threads / discuss / 8407

gitweb on shared hosting

Subject: gitweb on shared hosting

## tl;dr

2 messages between Jun 2, 2007 and Jun 3, 2007.

replies: 1people: 2as markdown or json

Mircea Bardac· Jun 2, 2007, 16:53 UTC · lore
Hi everybody,
I don't know if this is possible or not, but I'm trying with no results.

Is it possible to install gitweb on a shared hosting system, with no root access. Reading the INSTALL document reveals only information for configuration on build-time/install as root.

I expected it to be installable just as any other web application:
* get gitweb.cgi and related files + place them on the webserver
* modify a config file (gitweb.cgi) to update the paths + gitweb options
* (eventually) adjust server configuration for CGI in the wanted dir
DONE.

Also, having configuration information spread across several files (README/INSTALL/gitweb.cgi) doesn't help much.

It is also very strange to have README/"How to configure gitweb for your local system" saying "You can specify the following configuration variables when buiding GIT". That means I have to rebuild GIT (actually, only gitweb/gitweb.cgi) to configure gitweb => I need to download the sources by hand instead of using the already installed gitweb on my system (the one which came with the git package).

Is there any strong reason to have configuration at build-time at all? It would be a lot easier IMO to have it *just* by config files. I'm saying this because most of the install process is manual anyway (copying/moving files).

Many thanks, Mircea

-- 
http://mircea.bardac.net
Jakub Narebski· Jun 3, 2007, 18:36 UTC · re: Mircea Bardac · lore

Re: gitweb on shared hosting

Mircea Bardac wrote:
Show 6 quoted lines
> It is also very strange to have README/"How to configure gitweb for your local 
> system" saying "You can specify the following configuration variables when 
> buiding GIT". That means I have to rebuild GIT (actually, only 
> gitweb/gitweb.cgi) to configure gitweb => I need to download the sources by 
> hand instead of using the already installed gitweb on my system (the one 
> which came with the git package).

First, it is when building gitweb/gitweb.cgi from gitweb/gitweb.perl, but in practice that is just filling configuration in a few places. See the places in the source, and later you can edit gitweb.cgi by hand.

> Is there any strong reason to have configuration at build-time at all? It 
> would be a lot easier IMO to have it *just* by config files. I'm saying this 
> because most of the install process is manual anyway (copying/moving files).

You can override configuration using config file (with exception of name of config file), and put [almost] all configuration in config file.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

← back to recent threads