Re: [PATCH GSoC 2/3] git-instaweb: Configure it to work with a global server root and projects list

From: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Date: May 19, 2010, 08:58 UTC
Message-ID: <AANLkTimFrX6yE69ZNlZM11XJVNLS5rpbsdeNN984iNs7@mail.gmail.com>
In-Reply-To: <201005190105.59606.jnareb@gmail.com>

Show 13 quoted lines

>
> Well, I can understand that.
>
> There are two options how to resolve this issue without adding yet
> another script (although on the other hand git-web-gui / git-client
> could share code with git-instaweb just like git-difftool and
> git-mergetool do).
>
> First is to leave git-instaweb similar to how it is now, with pid file,
> server config file, gitweb config file, etc. in $GIT_DIR/gitweb, but
> if it is invoked outside any git repository, start it in "repository
> administration" mode, i.e. on the page that allows one to create new
> repository or clone repository.

But this solution requires starting of many apache servers on many ports which is quite complicated and even messier.

Show 5 quoted lines

> The alternate solution would be to follow the idea implemented in this
> patch, namely per-user pid file, gitweb config file, server config file
> etc. and the *list of projects* file in $HOME/.gitweb (or whenever
> XDG / FHS / LSB says it should be named), _but_ add an easy way to add
> a new project (a new repositoey) to list.

The feature *Adding repository to client* in my project proposal will take care of this.

>  Perhaps even make
> 'git instaweb', when run from inside git repository, add automatically
> current repository to list (unless it is present there already), and
> perhaps open 'summary' page for said repository.

Yeah, we can do that but I think I will do it in another commit.

> But independently on which solution would be chosen, it should take place
> in a separate commit,

So, I will implement the second solution but in seperate commit. First I will take care of this patch :)

Thanks
- Pavan