deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

compile, rc, doc/3: allow custom umask

Browse source
This commit is contained in:
Sitaram Chamarty 2009-09-21 14:41:37 +05:30
parent 838dd65d5f
commit df3dd0de48
3 changed files with 16 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
conf/example.gitolite.rc
View file

@ -16,6 +16,14 @@
$REPO_BASE="repositories"; $REPO_BASE="repositories";
# the default umask for repositories is 0077; change this if you run stuff
# like gitweb and find it can't read the repos. Please note the syntax; the
# leading 0 is required
$REPO_UMASK = 0077; # gets you 'rwx------'
# $REPO_UMASK = 0027; # gets you 'rwxr-x---'
# $REPO_UMASK = 0022; # gets you 'rwxr-xr-x'
# -------------------------------------- # --------------------------------------
# I see no reason anyone may want to change the gitolite admin directory, but # I see no reason anyone may want to change the gitolite admin directory, but

7
doc/3-faq-tips-etc.mkd
View file

@ -59,7 +59,7 @@ normal way, since it's not empty anymore.
* cloning an empty repo is only possible with clients greater than 1.6.2. * cloning an empty repo is only possible with clients greater than 1.6.2.
So at least one of your clients needs to have a recent git. Once at least So at least one of your clients needs to have a recent git. Once at least
one commit has been made, older clients can also use it. one commit has been made, older clients can also use it
* when you clone an empty repo, git seems to complain about the remote * when you clone an empty repo, git seems to complain about the remote
hanging up or something. I have no idea what that is, but it doesn't seem hanging up or something. I have no idea what that is, but it doesn't seem
@ -81,7 +81,10 @@ normal way, since it's not empty anymore.
automatically be committed. This is a simple safety net in case you automatically be committed. This is a simple safety net in case you
accidentally delete the whole config or something. Also see accidentally delete the whole config or something. Also see
[4-push-to-admin.mkd](http://github.com/sitaramc/gitolite/blob/pu/doc/4-push-to-admin.mkd) [4-push-to-admin.mkd](http://github.com/sitaramc/gitolite/blob/pu/doc/4-push-to-admin.mkd)
if you really know what you're doing and want "push to admin". if you really know what you're doing and want "push to admin"
* gitweb not able to read your repos? You can change the umask for newly
created repos to something more relaxed -- see the `~/.gitolite.rc` file
### differences from gitosis ### differences from gitosis

6
src/gl-compile-conf
View file

@ -41,7 +41,7 @@ use Data::Dumper;
# common definitions # common definitions
# ---------------------------------------------------------------------------- # ----------------------------------------------------------------------------
our ($GL_ADMINDIR, $GL_CONF, $GL_KEYDIR, $GL_CONF_COMPILED, $REPO_BASE); our ($GL_ADMINDIR, $GL_CONF, $GL_KEYDIR, $GL_CONF_COMPILED, $REPO_BASE, $REPO_UMASK);
# now that this thing *may* be run via "push to admin", any errors have to # now that this thing *may* be run via "push to admin", any errors have to
# grab the admin's ATTENTION so he won't miss them among the other messages a # grab the admin's ATTENTION so he won't miss them among the other messages a
@ -66,8 +66,8 @@ my $USERNAME_PATT=qr(^\@?[0-9a-zA-Z][0-9a-zA-Z._-]*$); # very simple patter
my %groups = (); my %groups = ();
my %repos = (); my %repos = ();
# set a restrictive umask, just in case # set the umask before creating any files
umask(0077); umask($REPO_UMASK);
# ---------------------------------------------------------------------------- # ----------------------------------------------------------------------------
# subroutines # subroutines