Documentation

diff --git a/docs/01_setup.mkd b/docs/01_setup.mkd
index c5d78defcc2415b000f51887bd75e778d774641e..75b51419315b99fbdc8cc4e6cab599e8904b4b1d 100644 (file)
--- a/docs/01_setup.mkd
+++ b/docs/01_setup.mkd
@@ -393,17 +393,23 @@ Like anything else, this design has pros and cons.
 2. you specify exactly what branches are indexed; experimental/dead/personal branches can be ignored\r
 \r
 #### Cons\r
-1. you have to opt-in a repository _after_ it is created and has some commits\r
-2. you specify exactly what branches are indexed\r
+1. you specify exactly what branches are indexed\r
 \r
-#### Why does Gitblit check every 2 mins for repository/branch changes?\r
+#### I have 300 repositories and you want me to specify indexed branches on each one??\r
 \r
-Gitblit has to balance its design as a complete, integrated Git server and its utility as a repository viewer in an existing Git setup.\r
+Yeah, I agree that is inconvenient.\r
 \r
-Gitblit could build indexes immediately on *edit repository* or on *receiving pushes*, but that design would not work if someone is pushing via ssh://, git://, or file:// (i.e. not pushing to Gitblit http(s)://).  For this reason Gitblit has a polling mechanism to check for ref changes every 2 mins.  This design works well for all use cases, aside from adding a little lag in updating the index.\r
+If you are using Gitblit GO there is a utility script `add-indexed-branch.cmd` which allows you to specify an indexed branch for many repositories in one step.\r
+\r
+If you are using Gitblit WAR then, at present, you are out of luck unless you write your own script to traverse your repositories and use native Git to manipulate each repository config.\r
+\r
+    git config --add gitblit.indexBranch "default"\r
+    git config --add gitblit.indexBranch "refs/heads/master"\r
 \r
 #### Indexing Branches\r
-You may specify which branches should be indexed per-repository in the *Edit Repository* page.  New/empty repositories can not pre-specify indexed branches; you can only specify indexed branches for a repository with commits.  Indexes are built and incrementally updated on a 2 minute cycle so you may have to wait a few minutes before your index is built or before your latest pushes get indexed.\r
+You may specify which branches should be indexed per-repository in the *Edit Repository* page.  New/empty repositories may only specify the *default* branch which will resolve to whatever commit HEAD points to or the most recently updated branch if HEAD is unresolvable.\r
+\r
+Indexes are built and incrementally updated on a 2 minute cycle so you may have to wait a few minutes before your index is built or before your latest pushes get indexed.\r
 \r
 **NOTE:**  \r
 After specifying branches, only the content from those branches can be searched via Gitblit.  Gitblit will automatically redirect any queries entered on a repository's search box to the Lucene search page. Repositories that do not specify any indexed branches will use the traditional commit-traversal search.\r
@@ -412,6 +418,12 @@ After specifying branches, only the content from those branches can be searched
 \r
 The initial indexing of an existing repository can potentially exhaust the memory allocated to your Java instance and may throw OutOfMemory exceptions.  Be sure to provide your Gitblit server adequate heap space to index your repositories.  The heap is set using the *-Xmx* JVM parameter in your Gitblit launch command (e.g. -Xmx1024M).\r
 \r
+#### Why does Gitblit check every 2 mins for repository/branch changes?\r
+\r
+Gitblit has to balance its design as a complete, integrated Git server and its utility as a repository viewer in an existing Git setup.\r
+\r
+Gitblit could build indexes immediately on *edit repository* or on *receiving pushes*, but that design would not work if someone is pushing via ssh://, git://, or file:// (i.e. not pushing to Gitblit http(s)://).  For this reason Gitblit has a polling mechanism to check for ref changes every 2 mins.  This design works well for all use cases, aside from adding a little lag in updating the index.\r
+\r
 ## Client Setup and Configuration\r
 ### Https with Self-Signed Certificates\r
 You must tell Git/JGit not to verify the self-signed certificate in order to perform any remote Git operations.\r

diff --git a/docs/04_releases.mkd b/docs/04_releases.mkd
index f4c182f677572c281d45562c0e0b01d220199a2c..5726f737e676fcd86f83f32b0f3ac5f6ba261f41 100644 (file)
--- a/docs/04_releases.mkd
+++ b/docs/04_releases.mkd
@@ -21,8 +21,9 @@
     **New:** *web.luceneIgnoreExtensions = 7z arc arj bin bmp dll doc docx exe gif gz jar jpg lib lzh odg odf odt pdf ppt png so swf xcf xls xlsx zip*  \r
 Repository branches may be optionally indexed by Lucene for improved searching.  To use this feature you must specify which branches to index within the *Edit Repository* page; _no repositories are automatically indexed_.  Gitblit will build or incrementally update enrolled repositories on a 2 minute cycle. (i.e you will have to wait 2-3 minutes after respecifying indexed branches or pushing new commits before Gitblit will build/update the repository's Lucene index.)  \r
 If a repository has Lucene-indexed branches the *search* form on the repository pages will redirect to the root-level Lucene search page and only the content of those branches can be searched.  \r
-If the repository does not specify any indexed branches then repository commit-traversal search is used.  \r
-**Note:** Initial indexing of an existing repository can be memory-exhaustive. Be sure to provide your Gitblit server adequate heap space to index your repositories (e.g. -Xmx1024M).\r
+If the repository does not specify any indexed branches then repository commit-traversal search is used.    \r
+**Note:** Initial indexing of an existing repository can be memory-exhaustive. Be sure to provide your Gitblit server adequate heap space to index your repositories (e.g. -Xmx1024M).  \r
+See the [setup](setup.html) page for additional details.\r
 - Allow specifying timezone to use for Gitblit which is independent of both the JVM and the system timezone (issue 54)  \r
     **New:** *web.timezone =*  \r
 - Added a built-in AJP connector for integrating Gitblit GO into an Apache mod_proxy setup (issue 59)  \r