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_war.mkd 2.2KB

11 years ago
11 years ago
123456789101112131415161718192021222324252627282930313233
  1. ## Upgrading Gitblit WAR (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 WAR (1.4.0+)
  11. The *baseFolder* context parameter has been replaced with a *baseFolder* JNDI env-entry. This means you can define the *baseFolder* from the administrative console of your servlet container and not have to manipulate anything in the web.xml file.
  12. ## Upgrading Gitblit WAR (1.2.1+)
  13. 1. Make sure your `WEB-INF/web.xml` *baseFolder* context parameter is not `${contextFolder}/WEB-INF/data`!
  14. If it is, move your `WEB-INF/data` folder to a location writeable by your servlet container.
  15. 2. Deploy new WAR
  16. 3. Edit the new WAR's `WEB-INF/web.xml` file and set the *baseFolder* context parameter to your external baseFolder.
  17. 4. Review and optionally apply any new settings as indicated in the [release log](releases.html) to `${baseFolder}/gitblit.properties`.
  18. ## Upgrading Gitblit WAR (pre-1.2.1)
  19. 1. Create a `data` as outlined in step 1 of *Upgrading Gitblit GO (pre-1.2.1)*
  20. 2. Copy your existing web.xml to your data folder
  21. 3. Deploy new WAR
  22. 4. Copy the new WAR's `WEB-INF/data/gitblit.properties` file to your data folder
  23. 5. Manually apply any changes you made to your original web.xml file to the gitblit.properties file you copied to your data folder
  24. 6. Edit the new WAR's `WEB-INF/web.xml` file and set the *baseFolder* context parameter to your external baseFolder.