The command line to start Gitblit has changed from
java -jar gitblit.jar --baseFolder data
to
java -cp "gitblit.jar:ext/*" com.gitblit.GitBlitServer --baseFolder data
or on Windows to
java -cp gitblit.jar;"%CD%\ext\*" com.gitblit.GitBlitServer --baseFolder data
The class path and main class need to be specified now. If you have installed Gitblit as a service you will need to adjust the service scripts or definitions accordingly.
The default gitblit.properties
file has been split into two files: gitblit.properties
, which is the recommended file for setting your configuration, and defaults.properties
which are Gitblit's default settings.
# Include Gitblit's 'defaults.properties' within your configuration.
#
# COMMA-DELIMITED
# SINCE 1.7.0
include = defaults.properties
Notice that the default settings are included by your gitblit.properties
file. The disadvantage to this approach is you must flip between discovering/reading the settings in defaults.properties
and setting them in gitblit.properties
, but there are some clear advantages too. This setup is not required. You may continue to keep all your settings in gitblit.properties
like before.
Additionally you may find it useful if you are maintaining several Gitblit instances to share common properties files.
data
folderdata/gitblit.properties
.In *nix systems or Windows Vista/7/8, there are other tricks you can play like symlinking the data
folder or symlinking the GO folder.
All platforms support the --baseFolder command-line argument.
Create a data
folder and copy the following files and folders to it:
gitblit.properties
file and adjust the following settings:
Unzip Gitblit GO to a new folder
data
folder and overwrite the folder of the same name in the just-unzipped versiondata/gitblit.properties
.NOTE: You may need to adjust your service definitions to include the --baseFolder data
argument.
You may need to delete your old service definition and install a new one depending on what has changed in the release.