From 69eeaa5a725d20c6460771e224e441e7de23bffe Mon Sep 17 00:00:00 2001 From: James Moger Date: Wed, 7 May 2014 13:02:02 -0400 Subject: [PATCH] Documentation --- README.markdown | 2 ++ build.xml | 12 ++++-------- src/site/faq.mkd | 8 ++++++++ src/site/setup_go.mkd | 4 +++- src/site/siteindex.mkd | 12 +++--------- 5 files changed, 20 insertions(+), 18 deletions(-) diff --git a/README.markdown b/README.markdown index fb8632f4..348afae4 100644 --- a/README.markdown +++ b/README.markdown @@ -4,6 +4,8 @@ Gitblit Gitblit is an open source, pure Java Git solution for managing, viewing, and serving [Git](http://git-scm.com) repositories. More information about Gitblit can be found [here](http://gitblit.com). +[ ![Download](https://api.bintray.com/packages/gitblit/releases/stable/images/download.png) ](https://bintray.com/gitblit/releases/stable/_latestVersion) + License ------- diff --git a/build.xml b/build.xml index 2fd49b80..8400aa42 100644 --- a/build.xml +++ b/build.xml @@ -52,7 +52,7 @@ - + @@ -611,17 +611,14 @@ - + - - - - + @@ -917,8 +914,7 @@ - - + diff --git a/src/site/faq.mkd b/src/site/faq.mkd index 1b522f82..160808d6 100644 --- a/src/site/faq.mkd +++ b/src/site/faq.mkd @@ -1,5 +1,13 @@ ## Troubleshooting +### push failed for branch (n/a (unpacker error)) + +This is a bug in JGit (issue-408). TLDR: Newer git clients are optimized to send less data on the wire. JGit expects complete data to be sent, but there are scenarios where native git can optimize-out sending objects. By default, JGit requires everything sent be complete and referenceable. + +If you experience this, the workaround is to temporarily disable the reachable check for the receive pack, push, and then re-enable the setting. + + git.checkReferencedObjectsAreReachable = false + ### Eclipse/Egit/JGit complains that it "can't open upload pack"? There are a few ways this can occur: diff --git a/src/site/setup_go.mkd b/src/site/setup_go.mkd index 51ca295d..f099cc04 100644 --- a/src/site/setup_go.mkd +++ b/src/site/setup_go.mkd @@ -5,7 +5,7 @@ 2. The server itself is configured through a simple text file. Open `data/gitblit.properties` in your favorite text editor and make sure to review and set: - *server.httpPort* and *server.httpsPort* - - *server.storePassword* + - *server.storePassword* (do not enter *#* characters) **https** is strongly recommended because passwords are insecurely transmitted form your browser/git client using Basic authentication! - *git.packedGitLimit* (set larger than the size of your largest repository) - *git.streamFileThreshold* (set larger than the size of your largest committed file) @@ -39,6 +39,8 @@ The EGit failure message is something like: If you want to serve your repositories to another machine over https then you will want to generate a new certificate for the hostname or ip address you are serving from. +**NOTE:** The Gitblit Authority is a GUI tool and will require X11 forwarding on headless UNIX boxes. + 1. `authority.cmd` or `java -jar authority.jar --baseFolder data` 2. Click the *new ssl certificate* button (red rosette in the toolbar in upper left of window) 3. Enter the hostname or ip address diff --git a/src/site/siteindex.mkd b/src/site/siteindex.mkd index 5f58fb04..f0be43b7 100644 --- a/src/site/siteindex.mkd +++ b/src/site/siteindex.mkd @@ -6,7 +6,7 @@ - Screenshots +
@@ -30,8 +30,6 @@ Gitblit is an open-source, pure Java stack for managing, viewing, and serving [Git][git] repositories. It's designed primarily as a tool for small workgroups who want to host centralized repositories. -You can browse the [stable demo site](https://demo-gitblit.rhcloud.com) or the [snapshot demo site](https://next-gitblit.rhcloud.com), both are hosted on [RedHat's OpenShift][rhcloud] cloud service. - ### GO: Single-Stack Solution *Gitblit GO* is an integrated, single-stack solution based on Jetty. @@ -40,18 +38,12 @@ You do not need Apache httpd, Perl, Git, or Gitweb. Should you want to use some This is what you should download if you want to go from zero to Git in less than 5 mins. -All dependencies are bundled. - ### WAR: For Your Servlet Container *Gitblit WAR* is what you should download if you already have a servlet container available that you wish to use. Jetty 6/7/8 and Tomcat 6/7 are known to work. Generally, any Servlet 2.5 or Servlet 3.0 container should work. -All dependencies are bundled. - ### Express: For the Cloud *Gitblit Express* is a prepared distribution for [RedHat's OpenShift][rhcloud] cloud service. -All dependencies are bundled. - ### You decide how to use Gitblit Gitblit can be used as a dumb repository viewer with no administrative controls or user accounts. @@ -62,9 +54,11 @@ Gitblit can be used without any other Git tooling (including actual Git) or it c Administrators can create and manage all repositories, user accounts, and teams from the *Web UI*. Administrators can create and manage all repositories, user accounts, and teams from the *JSON RPC interface* using the [Gitblit Manager](http://code.google.com/p/gitblit/downloads/detail?name=%MANAGER%) or your own custom tooling. +Administrators can create and manage all repositories, user accounts, and teams from the *command-line* using the [Powertools plugin](https://github.com/gitblit/gitblit-powertools-plugin). ### Integration with Your Infrastructure +- Extendable by plugins - Groovy push hook scripts - Pluggable user service mechanism - LDAP authentication with optional LDAP-controlled Team memberships -- 2.39.5