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 6651a8e96b Move repository ownership to the UserModel and prepare for project ownership 10 years ago
src Move repository ownership to the UserModel and prepare for project ownership 10 years ago
.checkstyle Stop Checkstyle from complaining 10 years ago
.classpath Update to javax.mail 1.5.1 10 years ago
.gitbugtraq Process bugtraq configuration in markup document rendering 10 years ago
.gitignore Update .gitignore 10 years ago
.gitmodules Simplified repository creation with a NewRepositoryPage 10 years ago
.project Preliminary implementation of server-side forking (issue 137) 11 years ago
HOME.md Documentation 10 years ago
LICENSE Selected Apache License. Dropped : from name. Its simpler. 13 years ago
NOTICE Documentation 10 years ago
README.markdown Documentation 10 years ago
build.moxie Update to Moxie 0.9.2 10 years ago
build.xml Add link to Gitblit's Docker file in the Docker registry 10 years ago
gitblit.iml Update to javax.mail 1.5.1 10 years ago
release.template Added buildMavenArtifacts target to release script template 10 years ago
releases.moxie Documentation 10 years ago

README.markdown

Gitblit

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

Contributing

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

Java Runtime Requirement

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

Getting help

Read the online documentation available at the Gitblit website Issues, binaries, & sources @ Google Code

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.