Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

next round of doc fixes

  • Loading branch information...
commit 9de22b0365c8a26a9f85035cc28fd88782333dd6 1 parent fc1837f
@sitaramc authored
View
5 cust.mkd
@@ -128,10 +128,13 @@ You can install any hooks except these:
* (gitolite-admin repo only) gitolite reserves the `post-update` hook.
+**NOTE**: if you want to install a hook in only a few specific repositories,
+do it directly on the server.
+
How/where to install them is described in detail in the "locations" section
above, especially [this][localcode] and [this][pushcode]. The summary is that
you put them in the "hooks/common" sub-directory within the directory whose
-name is given in the `LOCAL_CODE` rc variable.
+name is given in the `LOCAL_CODE` rc variable, then run `gitolite setup`.
### #sugar syntactic sugar
View
2  g2migr-example.mkd
@@ -187,7 +187,7 @@ Now go to your old clone, and push it:
To /home/g3/repositories/gitolite-admin.git
+ 7eb8163...1474770 master -> master (forced update)
-Aaha! I forgot to set `CONFIG_KEYS` (new name for `GL_GIT_CONFIG_KEYS`) in
+Aaha! I forgot to set `CONFIG_KEYS` (new name for `GL_GITCONFIG_KEYS`) in
the new rc file so fix that:
$ vim ~/.gitolite.rc
View
10 how.mkd
@@ -5,6 +5,16 @@ You'll appreciate this more if you first read the [try it and see][tias] page
[tias]: http://sitaramc.github.com/1-basic-usage/tias.html
+## what does a "gitolite repo" look like?
+
+A gitolite repo looks just like a normal bare repo on any normal git server.
+There are a few extra files placed in the repo directory whose names start
+with "gl-", and there is also an update hook placed in the hooks subdirectory,
+but that's about it, for the most part.
+
+In other words, you can treat a gitolite-managed repo just like any other bare
+repo as long as you leave those files alone.
+
## conventions used
--//--> network connection
View
6 master-toc.mkd
@@ -34,15 +34,15 @@
## [install][]
* notes and naming conventions
- * requirements
+ * [requirements][req]
* your skills
* server
* client
* getting the software
* the actual install
* upgrading
- * packaging gitolite
- * [migr][]ating
+ * [packaging][package] gitolite
+ * [migrating][migr] from v2
## [setup][]
View
5 non-core.mkd
@@ -1,5 +1,10 @@
# non-core programs shipped with gitolite
+**NOTE**: This doc describes *only some* of the non-core programs that come
+with gitolite. If you don't find what you want here, look in the appropriate
+directory (see the "locations" section in the [customisation][cust] document).
+Who knows, you might find some other cool feature you did not know about!
+
----
[[TOC]]
View
16 rules.mkd
@@ -43,11 +43,11 @@ there are lots of other possibilities.
There are 2 places where access rules are checked.
-The "pre-git" check is before git is invoked. Gitolite knows the repo name,
-user name, and attempted access (R or W), but no ref name.
+The "pre-git" check happens before git is invoked. Gitolite knows the repo
+name, user name, and attempted access (R or W), but no ref name.
-The "update" check is only for write operations, and it is just before git
-updates a ref. This time gitolite knows the refname also.
+The "update" check happens only for write operations, and it is just before
+git updates a ref. This time gitolite knows the refname also.
### how are the rules matched?
@@ -56,10 +56,10 @@ operation, and any permission that contains "W" matches a write operation.
This is because we simply don't know enough to make finer distinctions at this
point.
-In addition, *gitolite ignores deny rules during the pre-git check*. <font
-color="gray">(You can [change this][deny-rules] if you wish, though it's
-rarely needed)</font>. This means line 3 is ignored, and so Wally in our
-example will pass the pre-git check.
+Note that *gitolite ignores deny rules during the pre-git check*. This means
+line 3 is ignored, and so Wally in our example will pass the pre-git check.
+<font color="gray">(You can [change this][deny-rules] if you wish, though it's
+rarely needed)</font>.
For the **update check**, git gives us all the information we need. Then:
Please sign in to comment.
Something went wrong with that request. Please try again.