You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

upgrade_go.mkd 3.0KB

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