選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。

README.markdown 3.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  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://bintray.com/gitblit/releases/gitblit/_latestVersion'><img src='https://api.bintray.com/packages/gitblit/releases/gitblit/images/download.png'></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. | Google+ | +gitblit or +jamesmoger |
  21. Contributing
  22. ------------
  23. 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).
  24. Building Gitblit
  25. ----------------
  26. Gitblit uses submodules.
  27. Make sure to clone using `--recursive` OR to execute `git submodule update --init --recursive`.
  28. [Eclipse](http://eclipse.org) is recommended for development as the project settings are preconfigured.
  29. 1. Import the gitblit project into your Eclipse workspace.
  30. *There will be lots of build errors.*
  31. 2. Using Ant, execute the `build.xml` script in the project root.
  32. *This will download all necessary build dependencies and will also generate the Keys class for accessing settings.*
  33. 3. Select your gitblit project root and **Refresh** the project, this should correct all build problems.
  34. 4. Using JUnit, execute the `com.gitblit.tests.GitBlitSuite` test suite.
  35. *This will clone some repositories from the web and run through the unit tests.*
  36. 5. Execute the *com.gitblit.GitBlitServer* class to start Gitblit GO.
  37. Building Tips & Tricks
  38. ----------------------
  39. 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>
  40. 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.