You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.markdown 3.9KB

10 years ago
10 years ago
12 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
11 years ago
10 years ago
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768
  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/gitblit-org/gitblit/releases/latest' title='Download'><img alt='download badge' src='https://img.shields.io/badge/dynamic/json?color=9cf&label=Download&query=%24.name&url=https%3A%2F%2Fapi.github.com%2Frepos%2Fgitblit-org%2Fgitblit%2Freleases%2Flatest'></a>
  6. <a title='nightly docker' href='https://hub.docker.com/r/gitblit/gitblit/tags?page=1&name=nightly'><img alt='nightly docker badge' src='https://img.shields.io/badge/dynamic/json?color=2496ed&label=Nightly Docker&query=%24.tag_last_pushed&cacheSeconds=43200&url=https%3A%2F%2Fhub.docker.com%2Fv2%2Frepositories%2Fgitblit%2Fgitblit%2Ftags%2Fnightly'></a>
  7. ![License](https://img.shields.io/github/license/gitblit-org/gitblit?color=%23f29024)
  8. License
  9. -------
  10. Gitblit is distributed under the terms of the [Apache Software Foundation license, version 2.0](http://www.apache.org/licenses/LICENSE-2.0).
  11. The text of the license is included in the file LICENSE in the root of the project.
  12. Java Runtime Requirement
  13. ------------------------------------
  14. Gitblit requires a Java 8 Runtime Environment (JRE) or a Java 8 Development Kit (JDK).
  15. Getting help
  16. ------------
  17. | Source | Location |
  18. | ------------- |--------------------------------------------------------|
  19. | Documentation | [Gitblit website](http://gitblit.com) |
  20. | Forums | [Google Groups](https://groups.google.com/forum/#!forum/gitblit) |
  21. | Twitter | @gitblit or @jamesmoger |
  22. Contributing
  23. ------------
  24. 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).
  25. Please see the [CONTRIBUTING file](CONTRIBUTING.md) for suggestions and guidelines on contributing to Gitblit. Thank you!
  26. ### tl;dr
  27. 1. [Fork](https://github.com/gitblit-org/gitblit/fork) (and then `git clone https://github.com/gitblit-org/gitblit.git`).
  28. 2. Create a branch (`git checkout -b branch_name`).
  29. 3. Commit your changes (`git commit -a`).
  30. 4. Push to the branch (`git push origin branch_name`).
  31. 5. Open a Pull Request.
  32. Building Gitblit
  33. ----------------
  34. Gitblit uses submodules.
  35. Make sure to clone using `--recursive` OR to execute `git submodule update --init --recursive`.
  36. [Eclipse](http://eclipse.org) is recommended for development as the project settings are preconfigured.
  37. 1. Import the gitblit project into your Eclipse workspace.
  38. *There will be lots of build errors.*
  39. 2. Using Ant, execute the `build.xml` script in the project root.
  40. *This will download all necessary build dependencies and will also generate the Keys class for accessing settings.*
  41. 3. Select your gitblit project root and **Refresh** the project, this should correct all build problems.
  42. 4. Using JUnit, execute the `com.gitblit.tests.GitBlitSuite` test suite.
  43. *This will clone some repositories from the web and run through the unit tests.*
  44. 5. Execute the *com.gitblit.GitBlitServer* class to start Gitblit GO.
  45. Building Tips & Tricks
  46. ----------------------
  47. 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>
  48. 2. The build script will honor your Maven proxy settings. If you need to fine-tune this, please review the [settings.moxie](http://gitblit-org.github.io/moxie/settings.html) documentation.