| docs/00_index.mkd | ●●●●● patch | view | raw | blame | history | |
| docs/01_features.mkd | ●●●●● patch | view | raw | blame | history | |
| docs/01_setup.mkd | ●●●●● patch | view | raw | blame | history | |
| docs/site_header.html | ●●●●● patch | view | raw | blame | history |
docs/00_index.mkd
@@ -23,6 +23,10 @@ %VERSION% ([go](http://code.google.com/p/gitblit/downloads/detail?name=%GO%)|[war](http://code.google.com/p/gitblit/downloads/detail?name=%WAR%)) based on [%JGIT%][jgit] *released %BUILDDATE%* - clarified SSL certificate generation and configuration for both server-side and client-side - added some more troubleshooting information to documentation - replaced JavaService with Apache Commons Daemon issues & binaries @ [Google Code][googlecode]<br/> sources @ [Github][gitbltsrc]
@@ -48,20 +48,4 @@ - Gitblit may eat your data. Use at your own risk. - Gitblit may have security holes. Patches welcome. :) ## Todo List - Code documentation - Unit testing ### Under Consideration - Clone remote repository feature - Blob page improvements - view images - view other binary files (pdf, doc, etc) - Markdown editing feature - Stronger Ticgit read-only integration - activity/timeline - query feature with paging support - change history - Ticgit write integration [jgit]: http://eclipse.org/jgit "Eclipse JGit Site" docs/01_setup.mkd
@@ -87,6 +87,31 @@ **Example** java -jar gitblit.jar --userService c:\myrealm.properties --storePassword something ## Upgrading Gitblit Generally, upgrading is easy. Since Gitblit does not use a database the only files you have to worry about are your configuration file (`gitblit.properties` or `web.xml`) and possibly your `users.properties` file. Any important changes to the setting keys or default values will always be mentioned in the [release log](releases.html). ### Upgrading Gitblit WAR 1. Backup your `web.xml` file 2. Delete currently deployed gitblit WAR 3. Deploy new WAR and overwrite the `web.xml` file with your backup 4. Review and optionally apply any new settings as indicated in the [release log](releases.html). ### Upgrading Gitblit GO 1. Backup your `gitblit.properties` file 2. Backup your `users.properties` file *(if it is located in the Gitblit GO folder)* 3. Unzip Gitblit GO to a new folder 4. Overwrite the `gitblit.properties` file with your backup 5. Overwrite the `users.properties` file with your backup *(if it was located in the Gitblit GO folder)* 6. Review and optionally apply any new settings as indicated in the [release log](releases.html). #### Upgrading Windows Service You may need to delete your old service definition and install a new one depending on what has changed in the release. ## Gitblit Configuration
@@ -5,7 +5,7 @@ <link rel="stylesheet" type="text/css" href="./gitblit.css"/> <link rel="stylesheet" type="text/css" href="./markdown.css"/> <link rel="shortcut icon" type="image/png" href="./gitblt-favicon.png" /> <meta name="ROBOTS" content="INDEX, NOFOLLOW"> <meta name="ROBOTS" content="INDEX"> <meta http-equiv="imagetoolbar" content="no" /> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta name="keywords" content="java git server" />
