| commit | author | age | ||
| 17ae31 | 1 | ## Upgrading Gitblit GO (1.7.0+) |
| JM | 2 | |
| 3 | 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. | |
| 4 | ||
| 5 | # Include Gitblit's 'defaults.properties' within your configuration. | |
| 6 | # | |
| 7 | # COMMA-DELIMITED | |
| 8 | # SINCE 1.7.0 | |
| 9 | include = defaults.properties | |
| 10 | ||
| 11 | 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. | |
| 12 | ||
| 13 | Additionally you may find it useful if you are maintaining several Gitblit instances to share common properties files. | |
| 14 | ||
| 8c99a7 | 15 | ## Upgrading Gitblit GO (1.2.1+) |
| JM | 16 | |
| 17 | 1. Unzip Gitblit GO to a new folder | |
| 18 | 2. Set the *--baseFolder* argument to point to your old `data` folder | |
| 19 | 3. Review and optionally apply any new settings as indicated in the [release log](releases.html) to `data/gitblit.properties`. | |
| 20 | ||
| 21 | 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. | |
| 22 | All platforms support the *--baseFolder* command-line argument. | |
| 23 | ||
| 24 | ## Upgrading Gitblit GO (pre-1.2.1) | |
| 25 | 1. Create a `data` folder and copy the following files and folders to it: | |
| 6c4be1 | 26 | - **users.conf** |
| 8c99a7 | 27 | - **projects.conf** *(if you have one)* |
| JM | 28 | - **gitblit.properties** |
| 29 | - **serverKeystore.jks** | |
| 30 | - **serverTrustStore.jks** | |
| 6c4be1 | 31 | - **certs** folder |
| 8c99a7 | 32 | - **git** folder |
| JM | 33 | - **groovy** folder |
| 34 | - **proposals** folder | |
| 35 | - and any other custom files (robots.txt, welcome/login markdown files, etc) | |
| 36 | - then edit your `gitblit.properties` file and adjust the following settings: | |
| 37 | - *git.repositoriesFolder* = ${baseFolder}/git | |
| 38 | - *groovy.scriptsFolder* = ${baseFolder}/groovy | |
| 39 | - *groovy.grapeFolder* = ${baseFolder}/groovy/grape | |
| 40 | - *web.projectsFile* = ${baseFolder}/projects.conf | |
| 41 | - *realm.userService* = ${baseFolder}/users.conf | |
| 42 | - *web.robots.txt* = ${baseFolder}/robots.txt | |
| 43 | - *federation.proposalsFolder* = ${baseFolder}/proposals | |
| 44 | - *realm.ldap.backingUserService* = ${baseFolder}/users.conf | |
| 45 | - *realm.redmine.backingUserService* = ${baseFolder}/users.conf | |
| 46 | - *server.tempFolder* = ${baseFolder}/temp | |
| 47 | ||
| 48 | 2. Unzip Gitblit GO to a new folder | |
| 49 | 3. Copy your `data` folder and overwrite the folder of the same name in the just-unzipped version | |
| 50 | 4. Review and optionally apply any new settings as indicated in the [release log](releases.html) to `data/gitblit.properties`. | |
| 51 | ||
| 52 | **NOTE:** You may need to adjust your service definitions to include the `--baseFolder data` argument. | |
| 53 | ||
| 54 | #### Upgrading Windows Service | |
| 55 | You may need to delete your old service definition and install a new one depending on what has changed in the release. | |
| 56 | ||
