您最多选择25个主题 主题必须以字母或数字开头,可以包含连字符 (-),并且长度不得超过35个字符

11 年前
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
  1. Gitblit
  2. =================
  3. Gitblit is an open source, pure Java Git solution for managing, viewing, and serving [Git](http://git-scm.com) repositories. It can serve repositories over the GIT, HTTP, and SSH transports; it can authenticate against multiple providers; and it allows you to get up-and-running with an attractive, capable Git server in less than 5 minutes.
  4. More information about Gitblit can be found [here](http://gitblit.com).
  5. <a href='https://github.com/fzs/gitblit/releases/latest'><img src='https://img.shields.io/badge/dynamic/json?color=9cf&label=Download&query=%24.name&url=https%3A%2F%2Fapi.github.com%2Frepos%2Ffzs%2Fgitblit%2Freleases%2Flatest'></a>
  6. License
  7. -------
  8. Gitblit is distributed under the terms of the [Apache Software Foundation license, version 2.0](http://www.apache.org/licenses/LICENSE-2.0).
  9. The text of the license is included in the file LICENSE in the root of the project.
  10. Java Runtime Requirement
  11. ------------------------------------
  12. Gitblit requires at Java 7 Runtime Environment (JRE) or a Java 7 Development Kit (JDK).
  13. Getting help
  14. ------------
  15. | Source | Location |
  16. | ------------- |--------------------------------------------------------|
  17. | Documentation | [Gitblit website](http://gitblit.com) |
  18. | Forums | [Google Groups](https://groups.google.com/forum/#!forum/gitblit) |
  19. | Twitter | @gitblit or @jamesmoger |
  20. Contributing
  21. ------------
  22. GitHub pull requests are preferred. Any contributions must be distributed under the terms of the [Apache Software Foundation license, version 2.0](http://www.apache.org/licenses/LICENSE-2.0).
  23. Building Gitblit
  24. ----------------
  25. Gitblit uses submodules.
  26. Make sure to clone using `--recursive` OR to execute `git submodule update --init --recursive`.
  27. [Eclipse](http://eclipse.org) is recommended for development as the project settings are preconfigured.
  28. 1. Import the gitblit project into your Eclipse workspace.
  29. *There will be lots of build errors.*
  30. 2. Using Ant, execute the `build.xml` script in the project root.
  31. *This will download all necessary build dependencies and will also generate the Keys class for accessing settings.*
  32. 3. Select your gitblit project root and **Refresh** the project, this should correct all build problems.
  33. 4. Using JUnit, execute the `com.gitblit.tests.GitBlitSuite` test suite.
  34. *This will clone some repositories from the web and run through the unit tests.*
  35. 5. Execute the *com.gitblit.GitBlitServer* class to start Gitblit GO.
  36. Building Tips & Tricks
  37. ----------------------
  38. 1. If you are running Ant from an ANSI-capable console, consider setting the `MX_COLOR` environment variable before executing Ant.<pre>set MX_COLOR=true</pre>
  39. 2. The build script will honor your Maven proxy settings. If you need to fine-tune this, please review the [settings.moxie](http://gitblit.github.io/moxie/settings.html) documentation.