summaryrefslogtreecommitdiffstats
path: root/src/site/setup_client.mkd
diff options
context:
space:
mode:
authorJames Moger <james.moger@gitblit.com>2013-07-03 21:35:02 -0400
committerJames Moger <james.moger@gitblit.com>2013-07-03 21:35:02 -0400
commit8c99a7929b48b4c4a33c80d0b6646f6e6bb563b5 (patch)
treef0cce1420e9196339c612c2994d393455a23d365 /src/site/setup_client.mkd
parent5c5b7a8659851abc6ce1654414ceeef2e7f9c803 (diff)
downloadgitblit-8c99a7929b48b4c4a33c80d0b6646f6e6bb563b5.tar.gz
gitblit-8c99a7929b48b4c4a33c80d0b6646f6e6bb563b5.zip
Documentation
Diffstat (limited to 'src/site/setup_client.mkd')
-rw-r--r--src/site/setup_client.mkd46
1 files changed, 46 insertions, 0 deletions
diff --git a/src/site/setup_client.mkd b/src/site/setup_client.mkd
new file mode 100644
index 00000000..684cba21
--- /dev/null
+++ b/src/site/setup_client.mkd
@@ -0,0 +1,46 @@
+
+## Client Setup and Configuration
+### Https with Self-Signed Certificates
+You must tell Git/JGit not to verify the self-signed certificate in order to perform any remote Git operations.
+
+**NOTE:**
+The default self-signed certificate generated by Gitlbit GO is bound to *localhost*.
+If you are using Eclipse/EGit/JGit clients, you will have to generate your own certificate that specifies the exact hostname used in your clone/push url.
+You must do this because Eclipse/EGit/JGit (< 3.0) always verifies certificate hostnames, regardless of the *http.sslVerify=false* client-side setting.
+
+- **Eclipse/EGit/JGit**
+ 1. Window->Preferences->Team->Git->Configuration
+ 2. Click the *New Entry* button
+ 3. <pre>Key = <em>http.sslVerify</em>
+Value = <em>false</em></pre>
+- **Command-line Git** ([Git-Config Manual Page](http://www.kernel.org/pub/software/scm/git/docs/git-config.html))
+<pre>git config --global --bool --add http.sslVerify false</pre>
+
+### Http Post Buffer Size
+You may find the default post buffer of your git client is too small to push large deltas to Gitblit. Sometimes this can be observed on your client as *hanging* during a push. Other times it can be observed by git erroring out with a message like: error: RPC failed; result=52, HTTP code = 0.
+
+This can be adjusted on your client by changing the default post buffer size:
+<pre>git config --global http.postBuffer 524288000</pre>
+
+### Disabling SNI
+
+You may run into SNI alerts (Server Name Indication). These will manifest as failures to clone or push to your Gitblit instance.
+
+#### Java-based Clients
+
+When using Java 7-based clients, SNI is enabled by default. You can disable SNI by specifying the JVM system parameter `-Djsse.enableSNIExtension=false` when your Java-based client launches.
+
+For Eclipse, you can append `-Djsse.enableSNIExtension=false` to your *eclipse.ini* file.
+
+#### Native Clients
+
+Native clients may display an error when attempting to clone or push that looks like this:
+---FIXED---
+C:\projects\git\gitblit>git push rhcloud master
+error: error:14077458:SSL routines:SSL23_GET_SERVER_HELLO:reason(1112) while accessing https://demo-gitblit.rhcloud.com/git/gitblit.git/info/refs?service=git-receive-pack
+fatal: HTTP request failed
+---FIXED---
+
+### Cloning a Repository
+
+Gitblit provides many custom clone links for popular Git clients on the Summary page of each repository. If you have one or more of those clients installed, you should be able to click the link to initiate cloning with the selected tool.