(minor) less important docs have "## title" now
this is so the make-gh-pages (not part of gitolite) script can boldface the ones which have "# title"
This commit is contained in:
Sitaram Chamarty
parent
76ae0268fa
commit
6a5d564917
|
|
@ -25,9 +25,10 @@ And [here][who]'s some information on some of the projects and people using
|
|||
gitolite (and who, in turn, have helped shape its features).
|
||||
|
||||
Once you've installed it and started using it, you'll want to explore some of
|
||||
the more powerful features. All the documentation is available in the source
|
||||
repo as well as [online][docs]. All the longer documents have tables of
|
||||
contents, so you can quickly get a feel for what is covered right at the top.
|
||||
the more powerful features. **The documentation is best read [online
|
||||
here][docs] or you can read it in your clone's `doc/` directory**. All the
|
||||
longer documents have tables of contents, so you can quickly get a feel for
|
||||
what is covered right at the top.
|
||||
|
||||
----
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# comparing gerrit and gitolite
|
||||
## comparing gerrit and gitolite
|
||||
|
||||
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,
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# gitolite-tools
|
||||
## gitolite-tools
|
||||
|
||||
gitolite-tools is a collection of external git commands to work with
|
||||
gitolite server and repositories:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# ldap helper programs
|
||||
## ldap helper programs
|
||||
|
||||
These programs were contributed by the Nokia MeeGo folks.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Vim Syntax Highlight
|
||||
## Vim Syntax Highlight
|
||||
|
||||
[Vim][] Syntax highlight for `gitolite.conf` can be found from:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# admin defined commands
|
||||
## admin defined commands
|
||||
|
||||
**WARNING: Use this feature only if you really really know what you're doing.
|
||||
If you come back to me saying this feature caused a problem, I will only
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# what is a "big-config"
|
||||
## what is a "big-config"
|
||||
|
||||
In this document:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# delegating access control responsibilities
|
||||
## delegating access control responsibilities
|
||||
|
||||
[Thanks to jeromeag for forcing me to think through this...]
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# developer/patch maintainer notes
|
||||
## developer/patch maintainer notes
|
||||
|
||||
In this document:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# hook propagation in gitolite
|
||||
## hook propagation in gitolite
|
||||
|
||||
Advanced users need to know how hooks propagate, and when. They also need to
|
||||
know where to place their hooks, and since there appear to be two places to
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# mirroring a gitolite setup
|
||||
## mirroring a gitolite setup
|
||||
|
||||
Mirroring git repos is essentially a one-liner. For each mirror you want to
|
||||
update, you just add a post-receive hook that says
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# mob branches in gitolite
|
||||
## mob branches in gitolite
|
||||
|
||||
WARNING: This is hairy stuff. But what's life without a little danger?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
(contributed doc: integrating gitolite with monkeysphere)
|
||||
## (contributed doc: integrating gitolite with monkeysphere)
|
||||
|
||||
This document attempts to describe one way to integrate
|
||||
[Monkeysphere](http://web.monkeysphere.info/) authentication
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# when gitolite is overkill
|
||||
## when gitolite is overkill
|
||||
|
||||
Note: I wrote this to help people for whom gitolite is genuinely overkill. I
|
||||
believe it will all work, but YMMV.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# packaging gitolite
|
||||
## packaging gitolite
|
||||
|
||||
Here's how you'd package gitolite. In the following description, location "X"
|
||||
can be, say, `/usr/share/gitolite/conf` or some such, and similarly location
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
(master copy of progit chapter on gitolite)
|
||||
# (master copy of progit chapter on gitolite)
|
||||
|
||||
## Gitolite ##
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# avoiding the shell on the server
|
||||
## avoiding the shell on the server
|
||||
|
||||
Gitolite now tries to prevent gitolite-admin push privileges from being used
|
||||
to obtain a shell on the server. This was not always the case (older gitolite
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# uninstalling gitolite
|
||||
## uninstalling gitolite
|
||||
|
||||
Sometimes you might find gitolite is overkill -- you have only one user
|
||||
(yourself) pushing maybe. Or maybe gitolite is just not enough -- you want a
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# repositories named with wildcards
|
||||
## repositories named with wildcards
|
||||
|
||||
***IMPORTANT NOTE***:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# notes on the testing setup
|
||||
## notes on the testing setup
|
||||
|
||||
In this document:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue