7 Some gitolite features are enabled, or gitolite's behaviour changed, by
10 A line like 'option foo = 1' is really just syntactic sugar for 'config
11 gitolite-options.foo = 1', so everything in the [git-config][] page also
12 applies here (especially the bit about [overriding config
13 values][override_conf]).
15 **However**, these values are **not** written into git's own `config` file, so
16 git (or other programs running `git config`) will not see them. You can only
17 query them using `gitolite git-config`, where they will appear in full in the
20 Options are set by repo. The syntax is very simple:
26 Of course this is useless if some other part of gitolite, or some external
27 command, is not querying for the option key 'foo.bar'!
29 Options are therefore documented in the section/page they belong in, not here.
30 Here are some examples, although this list is not exhaustive:
32 * Ask gitolite to honor [deny rules][deny-rules] during the pre-git check
35 * [Mirroring][] related options -- tell gitolite who is the master server,
36 and who are the slaves, for each repo.
38 * The optional post-compile trigger 'update-gitweb-daemon-from-options'
39 allows you to use options instead of special usernames gitweb and daemon
40 to determine access for those tools.
42 * You can set [repo-specific environment variables][rsev] for triggers and
43 hooks to test, which is very useful.
45 Here's how to disable an option from a single repo if it was enabled earlier
46 in a group (which you might guess from reading the [git-config][] page):
54 # but repo r2 should not be accessible by gitweb