gitolite.rc 8.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233
  1. # paths and configuration variables for gitolite
  2. # please read comments before editing
  3. # this file is meant to be pulled into a perl program using "do" or "require".
  4. # You do NOT need to know perl to edit the paths; it should be fairly
  5. # self-explanatory and easy to maintain perl syntax :-)
  6. # --------------------------------------
  7. # Do not uncomment these values unless you know what you're doing
  8. # $GL_PACKAGE_CONF = "";
  9. # $GL_PACKAGE_HOOKS = "";
  10. # --------------------------------------
  11. # --------------------------------------
  12. # this is where the repos go. If you provide a relative path (not starting
  13. # with "/"), it's relative to your $HOME. You may want to put in something
  14. # like "/bigdisk" or whatever if your $HOME is too small for the repos, for
  15. # example
  16. $REPO_BASE="/srv/git/repositories/";
  17. # the default umask for repositories is 0077; change this if you run stuff
  18. # like gitweb and find it can't read the repos. Please note the syntax; the
  19. # leading 0 is required
  20. $REPO_UMASK = 0002;
  21. # $REPO_UMASK = 0027; # gets you 'rwxr-x---'
  22. # $REPO_UMASK = 0022; # gets you 'rwxr-xr-x'
  23. # part of the setup of gitweb is a variable called $projects_list (please see
  24. # gitweb documentation for more on this). Set this to the same value:
  25. $PROJECTS_LIST = $ENV{HOME} . "/projects.list";
  26. # --------------------------------------
  27. # I see no reason anyone may want to change the gitolite admin directory, but
  28. # feel free to do so. However, please note that it *must* be an *absolute*
  29. # path (i.e., starting with a "/" character)
  30. # gitolite admin directory, files, etc
  31. $GL_ADMINDIR="/etc/gitolite";
  32. # --------------------------------------
  33. # templates for location of the log files and format of their names
  34. # I prefer this template (note the %y and %m placeholders)
  35. # it produces files like `~/.gitolite/logs/gitolite-2009-09.log`
  36. $GL_LOGT="/var/log/gitolite/gitolite-%y-%m.log";
  37. # other choices are below, or you can make your own -- but PLEASE MAKE SURE
  38. # the directory exists and is writable; gitolite won't do that for you (unless
  39. # it is the default, which is "$GL_ADMINDIR/logs")
  40. # $GL_LOGT="$GL_ADMINDIR/logs/gitolite-%y-%m-%d.log";
  41. # $GL_LOGT="$GL_ADMINDIR/logs/gitolite-%y.log";
  42. # --------------------------------------
  43. # Please DO NOT change these three paths
  44. $GL_CONF="$GL_ADMINDIR/conf/gitolite.conf";
  45. $GL_KEYDIR="$GL_ADMINDIR/keydir";
  46. $GL_CONF_COMPILED="$GL_ADMINDIR/conf/gitolite.conf-compiled.pm";
  47. # --------------------------------------
  48. # if git on your server is on a standard path (that is
  49. # ssh git@server git --version
  50. # works), leave this setting as is. Otherwise, choose one of the
  51. # alternatives, or write your own
  52. $GIT_PATH="";
  53. # $GIT_PATH="/opt/bin/";
  54. # --------------------------------------
  55. # ----------------------------------------------------------------------
  56. # BIG CONFIG SETTINGS
  57. # Please read doc/big-config.mkd for details
  58. $GL_BIG_CONFIG = 1;
  59. $GL_NO_DAEMON_NO_GITWEB = 1;
  60. $GL_NO_CREATE_REPOS = 1;
  61. $GL_NO_SETUP_AUTHKEYS = 1;
  62. # ----------------------------------------------------------------------
  63. # SECURITY SENSITIVE SETTINGS
  64. #
  65. # Settings below this point may have security implications. That
  66. # usually means that I have not thought hard enough about all the
  67. # possible ways to crack security if these settings are enabled.
  68. # Please see details on each setting for specifics, if any.
  69. # ----------------------------------------------------------------------
  70. # --------------------------------------
  71. # ALLOW REPO ADMIN TO SET GITCONFIG KEYS
  72. #
  73. # Gitolite allows you to set git repo options using the "config" keyword; see
  74. # conf/example.conf for details and syntax.
  75. #
  76. # However, if you are in an installation where the repo admin does not (and
  77. # should not) have shell access to the server, then allowing him to set
  78. # arbitrary repo config options *may* be a security risk -- some config
  79. # settings may allow executing arbitrary commands.
  80. #
  81. # You have 3 choices. By default $GL_GITCONFIG_KEYS is left empty, which
  82. # completely disables this feature (meaning you cannot set git configs from
  83. # the repo config).
  84. $GL_GITCONFIG_KEYS = "";
  85. # The second choice is to give it a space separated list of settings you
  86. # consider safe. (These are actually treated as a set of regular expression
  87. # patterns, and any one of them must match). For example:
  88. # $GL_GITCONFIG_KEYS = "core\.logAllRefUpdates core\..*compression";
  89. # allows repo admins to set one of those 3 config keys (yes, that second
  90. # pattern matches two settings from "man git-config", if you look)
  91. #
  92. # The third choice (which you may have guessed already if you're familiar with
  93. # regular expressions) is to allow anything and everything:
  94. # $GL_GITCONFIG_KEYS = ".*";
  95. # --------------------------------------
  96. # EXTERNAL COMMAND HELPER -- HTPASSWD
  97. # security note: runs an external command (htpasswd) with specific arguments,
  98. # including a user-chosen "password".
  99. # if you want to enable the "htpasswd" command, give this the absolute path to
  100. # whatever file apache (etc) expect to find the passwords in.
  101. $HTPASSWD_FILE = "";
  102. # Look in doc/3 ("easier to link gitweb authorisation with gitolite" section)
  103. # for more details on using this feature.
  104. # --------------------------------------
  105. # EXTERNAL COMMAND HELPER -- RSYNC
  106. # security note: runs an external command (rsync) with specific arguments, all
  107. # presumably filled in correctly by the client-side rsync.
  108. # base path of all the files that are accessible via rsync. Must be an
  109. # absolute path. Leave it undefined or set to the empty string to disable the
  110. # rsync helper.
  111. $RSYNC_BASE = "";
  112. # $RSYNC_BASE = "/home/git/up-down";
  113. # $RSYNC_BASE = "/tmp/up-down";
  114. # --------------------------------------
  115. # EXTERNAL COMMAND HELPER -- SVNSERVE
  116. # security note: runs an external command (svnserve) with specific arguments,
  117. # as specified below. %u is substituted with the username.
  118. # This setting allows launching svnserve when requested by the ssh client.
  119. # This allows using the same SSH setup (hostname/username/public key) for both
  120. # SVN and git access. Leave it undefined or set to the empty string to disable
  121. # svnserve access.
  122. $SVNSERVE = "";
  123. # $SVNSERVE = "/usr/bin/svnserve -r /var/svn/ -t --tunnel-user=%u";
  124. # --------------------------------------
  125. # ALLOW REPO CONFIG TO USE WILDCARDS
  126. # security note: this used to in a separate "wildrepos" branch. You can
  127. # create repositories based on wild cards, give "ownership" to the specific
  128. # user who created it, allow him/her to hand out R and RW permissions to other
  129. # users to collaborate, etc. This is powerful stuff, and I've made it as
  130. # secure as I can, but it hasn't had the kind of rigorous line-by-line
  131. # analysis that the old "master" branch had.
  132. # This has now been rolled into master, with all the functionality gated by
  133. # this variable. Set this to 1 if you want to enable the wildrepos features.
  134. # Please see doc/4-wildcard-repositories.mkd for details.
  135. $GL_WILDREPOS = 0;
  136. # --------------------------------------
  137. # DEFAULT WILDCARD PERMISSIONS
  138. # If set, this value will be used as the default user-level permission rule of
  139. # new wildcard repositories. The user can change this value with the setperms command
  140. # as desired after repository creation; it is only a default. Note that @all can be
  141. # used here but is special; no other groups can be used in user-level permissions.
  142. # $GL_WILDREPOS_DEFPERMS = 'R = @all';
  143. # --------------------------------------
  144. # HOOK CHAINING
  145. # by default, the update hook in every repo chains to "update.secondary".
  146. # Similarly, the post-update hook in the admin repo chains to
  147. # "post-update.secondary". If you're fine with the defaults, there's no need
  148. # to do anything here. However, if you want to use different names or paths,
  149. # change these variables
  150. # $UPDATE_CHAINS_TO = "hooks/update.secondary";
  151. # $ADMIN_POST_UPDATE_CHAINS_TO = "hooks/post-update.secondary";
  152. # --------------------------------------
  153. # ADMIN DEFINED COMMANDS
  154. # WARNING: Use this feature only if (a) you really really know what you're
  155. # doing or (b) you really don't care too much about security. Please read
  156. # doc/admin-defined-commands.mkd for details.
  157. # $GL_ADC_PATH = "";
  158. # --------------------------------------
  159. # per perl rules, this should be the last line in such a file:
  160. 1;
  161. # Local variables:
  162. # mode: perl
  163. # End:
  164. # vim: set syn=perl: