Re: Make Gitweb behave like Apache mod_userdir
- From
Sylvain Rabot <sylvain@abstraction.fr>
- Date
- Nov 17, 2009, 15:51 UTC
- Message-ID
- <7fce93be0911170751r6d51ae7bn20fd593741b3eba6@mail.gmail.com>
- In-Reply-To
- <200911171458.56047.jnareb@gmail.com>
On Tue, Nov 17, 2009 at 14:58, Jakub Narebski <jnareb@gmail.com> wrote:
Show 14 quoted lines
> On Sun, 15 Nov 2009, Junio C Hamano wrote: >> Sylvain Rabot <sylvain@abstraction.fr> writes: >> >> > I made gitweb behave a bit like UserDir module will in apache. >> > In fact it's only configuration but I think it could be useful to others. >> >> Thanks. Any comment from gitweb gangs? > > I would respond earlier if it was submitted with patch inline in mail > body, and not attached. If it needs to be attached (because of MUA/MTA > linewrapping or encoding issues), it should use 8bit and not base64 > content transfer encoding, have 'text/plain' and not > 'application/octet-stream' content type, and "inline" and not "attachement" > in content disposition.
Sorry about that but I'm new in the git world and it is the first time I submit a patch.
Show 8 quoted lines
> It also lacks proper commit message (although email describes it quite > well) and signoff, as per Documentation/SubmittingPatches. > > I like this patch. More examples in gitweb/README are always good idea. > >> > Basicly it allows users of your server who use git to be able to use > > "Basically"
Oops
Show 29 quoted lines
> >> > gitweb to browse their own root project. E.G. : > > "For example" > >> > >> > Alice's private repos : >> > >> > /home/alice/git/product_a.git (cloned from /var/git/product_a.git) >> > /home/alice/git/product_b.git (cloned from /var/git/product_b.git) >> > /home/alice/git/product_c.git (cloned from /var/git/product_c.git) >> > >> > Alice's links to her repos which she wants to be able to browse with gitweb : > > "Alice links", or "Alice creates symbolic links" > >> > >> > /home/alice/gitweb/product_a -> /home/alice/git/product_a.git/.git >> > /home/alice/gitweb/product_c -> /home/alice/git/product_c.git/.git >> > >> > Bare repos : >> > >> > /var/git/product_a.git >> > /var/git/product_b.git >> > /var/git/product_c.git >> > /var/git/product_d.git > > The description is a bit lacking. Where user should put theirs git > repositories, or symbolic links to git repositories?
As I said It's only configuration so It depends of your server architecture. If admin of the server decides he allows users to browse via gitweb their private/public repos which are linked in /home/*/.gitweb or anything else he has to modify the environmental variable in the rewrite rule according to his wish.
> How it would look like in gitweb?
What do you mean ?
> -- > Jakub Narebski > Poland