...because gh-pages won't show files starting with an underscore :(
(and they replied saying "it's by design" so no expectation of a fix)
This commit is contained in:
parent
f6dd9dda0a
commit
582c1873e2
|
@ -35,7 +35,7 @@ Without the 'big config' setting, gitolite internally translates this to:
|
|||
|
||||
and then generates the actual config rules once for each user-repo-ref
|
||||
combination (there are 8 combinations above); the compiled config file looks
|
||||
somewhat like [this][_bigno].
|
||||
somewhat like [this][bigno__].
|
||||
|
||||
Of course, the output is the same whether you used groups (like `@wbr` and
|
||||
`@devs` in the example above) or listed the repos directly on the 'repo'
|
||||
|
@ -57,7 +57,7 @@ happens.
|
|||
### access rules for groups
|
||||
|
||||
If you used group names in the 'repo' lines (as in `repo @wbr`), then the
|
||||
compiled config looks like [this][_bigyes].
|
||||
compiled config looks like [this][bigyes__].
|
||||
|
||||
That's a lot smaller, and allows orders of magintude more repos and groups to
|
||||
be supported.
|
||||
|
@ -287,7 +287,7 @@ composite set of rules that 'alice' accessing 'lynx' is subject to.
|
|||
|
||||
## config listings
|
||||
|
||||
### F=_bigno compiled config with big-config disabled
|
||||
### F=bigno__ compiled config with big-config disabled
|
||||
|
||||
%repos = (
|
||||
'firefox' => {
|
||||
|
@ -362,7 +362,7 @@ composite set of rules that 'alice' accessing 'lynx' is subject to.
|
|||
|
||||
Phew!
|
||||
|
||||
### F=_bigyes compiled config with big-config enabled
|
||||
### F=bigyes__ compiled config with big-config enabled
|
||||
|
||||
%repos = (
|
||||
'@wbr' => {
|
||||
|
|
|
@ -392,7 +392,7 @@ one of `-`, `R`, `RW`, `RW+`, `RWC`, `RW+C`, `RWD`, `RW+D`, `RWCD`, or
|
|||
the standalone `C`, which is not really a "ref" level permission and can be
|
||||
found in doc/wildcard-repositories.mkd.]
|
||||
|
||||
## F=_confother other tips
|
||||
## F=confother__ other tips
|
||||
|
||||
### personal branches
|
||||
|
||||
|
|
|
@ -95,7 +95,7 @@ summary":
|
|||
httpd if you prefer (this may require root access).
|
||||
* several other neat features, too many to list here
|
||||
|
||||
## F=_need why is gitolite needed?
|
||||
## F=need__ why is gitolite needed?
|
||||
|
||||
Gitolite is separate from git, and needs to be installed and configured. So...
|
||||
why do we bother?
|
||||
|
@ -153,7 +153,7 @@ deleting a branch (which is really just an extreme form of rewind). I needed
|
|||
something in between allowing anyone to do it (the default) and disabling it
|
||||
completely (`receive.denyNonFastForwards` or `receive.denyDeletes`).
|
||||
|
||||
### F=_morefeatures some more features
|
||||
### F=morefeatures__ some more features
|
||||
|
||||
Here're some more features.
|
||||
|
||||
|
|
|
@ -275,7 +275,7 @@ don't know ssh it'll be a nightmare to support you.
|
|||
* regular expressions are a big part of gitolite in many places but
|
||||
familiarity is not necessary to do basic access control.
|
||||
|
||||
### F=_getgl getting the gitolite software
|
||||
### F=getgl__ getting the gitolite software
|
||||
|
||||
You can get the latest version of gitolite from github or google code using
|
||||
the 'git clone' command:
|
||||
|
@ -351,7 +351,7 @@ here's how to clean the slate.
|
|||
delete `/var/gitolite/conf` and `/var/gitolite/hooks` or
|
||||
`$HOME/share/gitolite/conf` and `$HOME/share/gitolite/hooks`
|
||||
|
||||
### F=_uninstall appendix c: uninstalling gitolite completely
|
||||
### F=uninstall__ appendix c: uninstalling gitolite completely
|
||||
|
||||
(There's some duplication between this and the previous section).
|
||||
|
||||
|
|
|
@ -92,7 +92,7 @@ and the corresponding derived usernames:
|
|||
sitaramc@gmail.com@laptop.pub sitaramc@gmail.com
|
||||
sitaramc@gmail.com@desktop.pub sitaramc@gmail.com
|
||||
|
||||
### F=_tipssec security, access control, and auditing
|
||||
### F=tipssec__ security, access control, and auditing
|
||||
|
||||
#### #2levels two levels of access rights checking
|
||||
|
||||
|
@ -160,7 +160,7 @@ that matched, in case you need to debug the config file itself.
|
|||
You can now split up the config file and delegate the authority to specify
|
||||
access control for their own pieces. See [delegation][deleg] for details.
|
||||
|
||||
### F=_tnconv convenience features
|
||||
### F=tnconv__ convenience features
|
||||
|
||||
#### what repos do I have access to?
|
||||
|
||||
|
|
|
@ -237,7 +237,7 @@ to install/setup "adc"s (admin defined commands). See
|
|||
Enjoy, and please use with care. This is pretty powerful stuff. As they say:
|
||||
if you break it, you get to keep both pieces :)
|
||||
|
||||
## F=_wildhow how it actually works
|
||||
## F=wildhow__ how it actually works
|
||||
|
||||
This section tells you what is happening inside gitolite so you can understand
|
||||
this feature better. Let's use the config example at the beginning of this
|
||||
|
|
Loading…
Reference in a new issue