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.
James Moger 855a19a242 Merge pull request #1153 from pingunaut/wicket-7 7 years ago
src Updated to latest wicket milestone and fix upgrade errors 7 years ago
.checkstyle Stop Checkstyle from complaining 10 years ago
.classpath Fix bootstrap and angular resources 7 years ago
.gitbugtraq Process bugtraq configuration in markup document rendering 10 years ago
.gitignore switched to java 8 and wicket 7.4.0 7 years ago
.gitmodules Document edit capability via ProseMirror submodule #974 8 years ago
.mailmap Add .mailmap 8 years ago
.project switched to java 8 and wicket 7.4.0 7 years ago
HOME.md fix for #967 filestore menu for all users 8 years ago
LICENSE Selected Apache License. Dropped : from name. Its simpler. 13 years ago
NOTICE Documentation 9 years ago
README.markdown Simplify build and contribution process back to master/trunk development 8 years ago
build.moxie Updated to latest wicket milestone and fix upgrade errors 7 years ago
build.xml Specify encoding of javadoc to "utf-8" 8 years ago
gitblit.iml switched to java 8 and wicket 7.4.0 7 years ago
release.template Simplify build and contribution process back to master/trunk development 8 years ago
releases.moxie Reset build identifiers for next point release cycle 7 years ago

README.markdown

Gitblit

Gitblit is an open source, pure Java Git solution for managing, viewing, and serving Git 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.

More information about Gitblit can be found here.

License

Gitblit is distributed under the terms of the Apache Software Foundation license, version 2.0. The text of the license is included in the file LICENSE in the root of the project.

Java Runtime Requirement

Gitblit requires at Java 7 Runtime Environment (JRE) or a Java 7 Development Kit (JDK).

Getting help

Source Location
Documentation Gitblit website
Forums Google Groups
Twitter @gitblit or @jamesmoger
Google+ +gitblit or +jamesmoger

Contributing

GitHub pull requests are preferred. Any contributions must be distributed under the terms of the Apache Software Foundation license, version 2.0.

Building Gitblit

Gitblit uses submodules. Make sure to clone using --recursive OR to execute git submodule update --init --recursive.

Eclipse is recommended for development as the project settings are preconfigured.

  1. Import the gitblit project into your Eclipse workspace. There will be lots of build errors.
  2. Using Ant, execute the build.xml script in the project root. This will download all necessary build dependencies and will also generate the Keys class for accessing settings.
  3. Select your gitblit project root and Refresh the project, this should correct all build problems.
  4. Using JUnit, execute the com.gitblit.tests.GitBlitSuite test suite. This will clone some repositories from the web and run through the unit tests.
  5. Execute the com.gitblit.GitBlitServer class to start Gitblit GO.

Building Tips & Tricks

  1. If you are running Ant from an ANSI-capable console, consider setting the MX_COLOR environment variable before executing Ant.
    set MX_COLOR=true
  2. The build script will honor your Maven proxy settings. If you need to fine-tune this, please review the settings.moxie documentation.