RE: Git-daemon messing up permissions for gitweb

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

RE: Git-daemon messing up permissions for gitweb

From: Post, Mark K <hidden>
Date: 2016-06-15 22:42:29

I just triple-checked, and both those things are already in place.  The
default umask is 0022, and all the config files have:
[core]
        repositoryformatversion = 0
        filemode = true
        sharedrepository = true

I see that the case of the value is different from what you typed:
SharedRepository 
Is that significant (as almost everything is)?


Mark Post

-----Original Message-----
From: Linus Torvalds [mailto:torvalds@osdl.org] 
Sent: Friday, June 09, 2006 3:06 PM
To: Post, Mark K
Cc: git@vger.kernel.org
Subject: Re: Git-daemon messing up permissions for gitweb



On Fri, 9 Jun 2006, Post, Mark K wrote:
As far as I can tell, the problem is happening because these files are
being written out with file permissions of 640, and since Apache is
running as user wwwrun, it can't read them:
You can either make sure that people have something like

	umask 0022

in their bashrc (or that it's the default umask), so that they do things

world-readably by default.

Or add
	[core]
		SharedRepository = true

to the repository config file.

		Linus

RE: Git-daemon messing up permissions for gitweb

From: Jakub Narebski <hidden>
Date: 2016-06-15 22:42:29

Post, Mark K wrote:
[core]
        repositoryformatversion = 0
        filemode = true
        sharedrepository = true

I see that the case of the value is different from what you typed:
        SharedRepository = true
Is that significant (as almost everything is)?
No, the keys are case-insensitive.

-- 
Jakub Narebski
Warsaw, Poland
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help