(minor) doc updates
This commit is contained in:
parent
2eaa2c6416
commit
6c682721b5
|
@ -2,7 +2,9 @@
|
|||
|
||||
Gerrit and gitolite have too many high level differences. Size is most
|
||||
visible of course: 56000 lines of Java versus 1300 lines of perl+shell,
|
||||
according to David A. Wheeler's 'SLOCCount' tool. Gerrit needs a database,
|
||||
according to David A. Wheeler's 'SLOCCount' tool. Gerrit needs a database (it
|
||||
comes with a perfectly usable one, or I believe you can use any of the usual
|
||||
suspects),
|
||||
and even comes with its own ssh server and git server, and since the git
|
||||
engine is internal it probably has to include a lot of things that normal git
|
||||
already has; I wouldn't know for sure.
|
||||
|
|
|
@ -19,6 +19,7 @@ workarounds I may not have the time to code it right away.
|
|||
|
||||
In this document:
|
||||
|
||||
* rc file setting required
|
||||
* wildcard repos
|
||||
* wildcard repos with creator name in them
|
||||
* wildcard repos without creator name in them
|
||||
|
@ -34,6 +35,12 @@ This document is mostly "by example".
|
|||
|
||||
----
|
||||
|
||||
### rc file setting required
|
||||
|
||||
This feature requires that you set `$GL_WILDREPOS` to "1" in `~/.gitolite.rc`
|
||||
on the server. Please search for that variable and see comments around it in
|
||||
`conf/example.gitolite.rc` for more information on this.
|
||||
|
||||
### Wildcard repos
|
||||
|
||||
Which of these alternatives you choose depends on your needs, and the social
|
||||
|
|
|
@ -45,7 +45,9 @@ on "restricted admin" for what's really exciting about this for *me*.
|
|||
----
|
||||
|
||||
It may be a good idea to read [doc/4-wildcard-repositories.mkd][wild] before
|
||||
you continue here though, because this feature builds on top of that.
|
||||
you continue here though, because most of the uses of this feature also need
|
||||
wildcard repos. (This also means you must set `$GL_WILDREPOS` to "1" in the
|
||||
rc file).
|
||||
|
||||
[wild]: http://github.com/sitaramc/gitolite/blob/pu/doc/4-wildcard-repositories.mkd
|
||||
|
||||
|
@ -190,3 +192,6 @@ as you can see, it cleverly makes use of the fact that you can now check for
|
|||
the invoking uses access to any repo in the system. In this case it checks if
|
||||
he has "W" access to the gitolite-admin repo, and if he does, allows the
|
||||
script to proceed.
|
||||
|
||||
[Note that this particular use does not require `$GL_WILDREPOS` to be enabled,
|
||||
because it's not using any wildcard repos].
|
||||
|
|
|
@ -568,7 +568,7 @@ v_done="
|
|||
done!
|
||||
|
||||
IMPORTANT NOTE -- PLEASE READ!!!
|
||||
*Your* URL for cloning any repo on this server will be
|
||||
*Your* URL for cloning any repo from this server will be
|
||||
gitolite:reponame.git
|
||||
|
||||
*Other* users you set up will have to use
|
||||
|
|
Loading…
Reference in a new issue