| commit | author | age | ||
| 8c99a7 | 1 | ## Gitblit WAR Installation & Setup |
| JM | 2 | |
| 3 | 1. Download Gitblit WAR [${project.releaseVersion}](%GCURL%gitblit-${project.releaseVersion}.war) to the webapps folder of your servlet container. | |
| 4 | 2. You may have to manually extract the WAR (zip file) to a folder within your webapps folder. | |
| 6c4be1 | 5 | 3. By default, the Gitblit webapp is configured through `WEB-INF/data/gitblit.properties`. |
| 8c99a7 | 6 | Open `WEB-INF/data/gitblit.properties` in your favorite text editor and make sure to review and set: |
| c72b44 | 7 | - *git.packedGitLimit* (set larger than the size of your largest repository) |
| 8c99a7 | 8 | 4. You may have to restart your servlet container. |
| JM | 9 | 5. Open your browser to <http://localhost/gitblit> or whatever the url should be. |
| 10 | 6. Enter the default administrator credentials: **admin / admin** and click the *Login* button | |
| 11 | **NOTE:** Make sure to change the administrator username and/or password!! | |
| 12 | ||
| 13 | ### WAR Data Location | |
| b5d532 | 14 | By default, Gitblit WAR stores all data (users, settings, repositories, etc) in `${contextFolder}/WEB-INF/data`. This is fine for a quick setup, but there are many reasons why you don't want to keep your data within the webapps folder of your servlet container. Specifying an alternate *baseFolder* also allows for simple upgrades in the future. |
| 8c99a7 | 15 | |
| b5d532 | 16 | Choose a location that is writeable by your servlet container! |
| 8c99a7 | 17 | |
| b5d532 | 18 | After you configure baseFolder and restart your container, Gitblit will copy the contents of the `WEB-INF/data` folder to your specified *baseFolder* **IF** the file `${baseFolder}/gitblit.properties` does not already exist. This allows you to get going with minimal fuss. |
| 8c99a7 | 19 | |
| 8a8bc3 | 20 | #### Specifying baseFolder via GITBLIT_HOME |
| JM | 21 | |
| 22 | You can specify `GITBLIT_HOME` either as an environment variable or as a `-DGITBLIT_HOME` JVM system property. | |
| 23 | ||
| 24 | #### Specifying baseFolder via web.xml | |
| b5d532 | 25 | |
| JM | 26 | You may specify an external location for your data by directly editing `WEB-INF/web.xml` and manipulating the *baseFolder* env-entry. Your servlet container may be smart enough to recognize the change and to restart Gitblit. |
| 27 | ||
| 8a8bc3 | 28 | #### Specifying baseFolder via JNDI |
| b5d532 | 29 | |
| JM | 30 | This is a better way to configure your *baseFolder* because it survives WAR redeploys or deployments of new versions. These directions assume you are running Tomcat as your container, other containers may have different ways to specify global JNDI environment entries. |
| 31 | ||
| 32 | 1. Open TOMCAT_HOME/conf/context.xml | |
| 33 | 2. Insert an *Environment* node within the *Context* node.<pre><Environment name="baseFolder" type="java.lang.String" value="c:/projects/git/gitblit/data" override="false" /></pre> | |
| 17ae31 | 34 | |
| JM | 35 | ### Including Other Properties |
| 36 | SINCE 1.7.0 | |
| 37 | ||
| 38 | Gitblit supports loading it's settings from multiple properties files. You can achieve this using the `include=filename` key. This setting supports loading multiple files using a *comma* as the delimiter. They are processed in the order defined and they may be nested (i.e. your included properties may include properties, etc, etc). | |
