blob: 4bc2272f4e6efcdba2c401c132779b2aaa28bea7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
## Upgrading Gitblit GO (1.9.1+)
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.
## Upgrading Gitblit GO (1.7.0+)
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.
## Upgrading Gitblit GO (1.2.1+)
1. Unzip Gitblit GO to a new folder
2. Set the *--baseFolder* argument to point to your old `data` folder
3. Review and optionally apply any new settings as indicated in the [release log](releases.html) to `data/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.
## Upgrading Gitblit GO (pre-1.2.1)
1. Create a `data` folder and copy the following files and folders to it:
- **users.conf**
- **projects.conf** *(if you have one)*
- **gitblit.properties**
- **serverKeystore.jks**
- **serverTrustStore.jks**
- **certs** folder
- **git** folder
- **groovy** folder
- **proposals** folder
- and any other custom files (robots.txt, welcome/login markdown files, etc)
- then edit your `gitblit.properties` file and adjust the following settings:
- *git.repositoriesFolder* = ${baseFolder}/git
- *groovy.scriptsFolder* = ${baseFolder}/groovy
- *groovy.grapeFolder* = ${baseFolder}/groovy/grape
- *web.projectsFile* = ${baseFolder}/projects.conf
- *realm.userService* = ${baseFolder}/users.conf
- *web.robots.txt* = ${baseFolder}/robots.txt
- *federation.proposalsFolder* = ${baseFolder}/proposals
- *realm.ldap.backingUserService* = ${baseFolder}/users.conf
- *realm.redmine.backingUserService* = ${baseFolder}/users.conf
- *server.tempFolder* = ${baseFolder}/temp
2. Unzip Gitblit GO to a new folder
3. Copy your `data` folder and overwrite the folder of the same name in the just-unzipped version
4. Review and optionally apply any new settings as indicated in the [release log](releases.html) to `data/gitblit.properties`.
**NOTE:** You may need to adjust your service definitions to include the `--baseFolder data` argument.
#### Upgrading Windows Service
You may need to delete your old service definition and install a new one depending on what has changed in the release.
|
