Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

with a gitolite configuration like this:

    repo    users/CREATOR/.+
            C       =   @defaultgroup
            RW+D    =   CREATOR
            RWD     =   @defaultgroup

the users of our server can easily create their own repositories just by cloning the "to be created" repo - e.g. with:

    git clone

This also shows up in our gitweb. But what's missing is some git configuration. I haven't been able to figure out how I could add working configuration to these newly created repositories (e.g. gitweb.url)?

Just for comparison - this is how a "normal" repo would look like:

    repo    normal/repo
            R       =   @all
            RW      =   @defaultgroup
            config  gitweb.url =
            config  receive.denyNonFastforwards = true

Any hints welcome, Cheers.

share|improve this question
up vote 1 down vote accepted

From the gitolite config page:

You can also use the special values %GL_REPO and %GL_CREATOR in the string.
The former is available to all repos, while the latter is only available to wild repos.

So this could work (not tested):

config  gitweb.url =
config  receive.denyNonFastforwards = true

(I suppose the last line would apply to all wild repos created under repo users/CREATOR/.+)

share|improve this answer
Solution was right for Gitolite 3 - unfortunately version2 doesn't support equal options. – pagid Oct 26 '12 at 22:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.