blob: 4165ca10dbfd66a68e7a249d69a1b0e2cadc5b13 [file] [log] [blame]
## Upgrading Gitblit WAR (1.7.0+)
The default `` file has been split into two files: ``, which is the recommended file for setting your configuration, and `` which are Gitblit's default settings.
# Include Gitblit's '' within your configuration.
# SINCE 1.7.0
include =
Notice that the default settings are *included* by your `` file. The disadvantage to this approach is you must flip between discovering/reading the settings in `` and setting them in ``, but there are some clear advantages too. This setup is not required. You may continue to keep all your settings in `` like before.
Additionally you may find it useful if you are maintaining several Gitblit instances to share common properties files.
## Upgrading Gitblit WAR (1.4.0+)
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.
## Upgrading Gitblit WAR (1.2.1+)
1. Make sure your `WEB-INF/web.xml` *baseFolder* context parameter is not `${contextFolder}/WEB-INF/data`!
If it is, move your `WEB-INF/data` folder to a location writeable by your servlet container.
2. Deploy new WAR
3. Edit the new WAR's `WEB-INF/web.xml` file and set the *baseFolder* context parameter to your external baseFolder.
4. Review and optionally apply any new settings as indicated in the [release log](releases.html) to `${baseFolder}/`.
## Upgrading Gitblit WAR (pre-1.2.1)
1. Create a `data` as outlined in step 1 of *Upgrading Gitblit GO (pre-1.2.1)*
2. Copy your existing web.xml to your data folder
3. Deploy new WAR
4. Copy the new WAR's `WEB-INF/data/` file to your data folder
5. Manually apply any changes you made to your original web.xml file to the file you copied to your data folder
6. Edit the new WAR's `WEB-INF/web.xml` file and set the *baseFolder* context parameter to your external baseFolder.