diff options
author | James Moger <james.moger@gitblit.com> | 2013-07-24 11:50:50 -0400 |
---|---|---|
committer | James Moger <james.moger@gitblit.com> | 2013-07-24 11:50:50 -0400 |
commit | 9359865cf1571d69a464387abb2b0b2c4982580d (patch) | |
tree | b2b953305ca07816ae24af5e8a79ff4049fcea79 /src/site | |
parent | adc821981f61927a78d7e0157f790e15343284af (diff) | |
download | gitblit-9359865cf1571d69a464387abb2b0b2c4982580d.tar.gz gitblit-9359865cf1571d69a464387abb2b0b2c4982580d.zip |
Documentation
Diffstat (limited to 'src/site')
-rw-r--r-- | src/site/setup_client.mkd | 2 | ||||
-rw-r--r-- | src/site/setup_express.mkd | 22 |
2 files changed, 16 insertions, 8 deletions
diff --git a/src/site/setup_client.mkd b/src/site/setup_client.mkd index 684cba21..e72751a1 100644 --- a/src/site/setup_client.mkd +++ b/src/site/setup_client.mkd @@ -28,7 +28,7 @@ You may run into SNI alerts (Server Name Indication). These will manifest as fa #### 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.
+Luckily, Java 6-based clients ignore SNI alerts but when using Java 7-based clients, SNI checking is enabled by default. You can disable SNI alerts 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.
diff --git a/src/site/setup_express.mkd b/src/site/setup_express.mkd index 6753542c..cf3ef659 100644 --- a/src/site/setup_express.mkd +++ b/src/site/setup_express.mkd @@ -10,6 +10,10 @@ as Gitblit Express is not a source distribution to be built with Maven on OpenSh Gitblit automatically adjusts itself to running on OpenShift. Repositories, users,
federation proposals, setting overrides, and Groovy push scripts are stored in *OPENSHIFT_DATA_DIR*.
+### Recommended Settings
+
+You should disable the git daemon by setting *git.daemonPort=0*.
+
It is recommended to enable all RPC settings in the `web.xml` file to allow remote
administration and, more importantly, configuration of your Gitblit Express
installation using the Gitblit Manager.
@@ -25,16 +29,20 @@ doing: - *groovy.scriptsFolder*
- *federation.proposalsFolder*
- *realm.userService* (for standard users.conf)
-
-Additionally, it is recommended to force your Gitblit installation to cleanup up
-older versions on your OpenShift filesystem to maximize available space for your
-repositories.
-Append the following command to your ./openshift/action_hooks/build file:
+### Native Git Failures
+
+Unfortunately, sometime in early 2013 RedHat changed their SSL certificate such that cloning from/pushing to Gitblit Express over https fails due to an SNI (server name indication) TLS alert. There is no known workaround for native git and https.
+
+However, if your git client is JGit-based, like Eclipse/EGit, then you can workaround this problem and happily push/clone using https and OpenShift.
+
+Luckily, Java 6-based clients ignore SNI alerts but when using Java 7-based clients, SNI checking is enabled by default. You can disable SNI alerts 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.
- rm -fr $OPENSHIFT_APP_DIR/jbossas-7.0/standalone/tmp/vfs/*
+### Heap and PermGen
-Lastly, you may want to play with the heap and permgen settings of your Gitblit
+You may want to play with the heap and permgen settings of your Gitblit
instance because the default heap for the JVM is 95 MB, which may be a little
tight.
|