| | |
|---|
| | | http://192.168.1.2/log/myrepo.git/refs%2Fheads%2Fmaster
|
|---|
| | |
|
|---|
| | | **NOTE:**
|
|---|
| | | You can not trust the url in the address bar of your browser since your browser may *prettify* the url. When in doubt, *View Source* of the generated html to confirm the *href*.
|
|---|
| | | You can not trust the url in the address bar of your browser since your browser may decode it for presentation. When in doubt, *View Source* of the generated html to confirm the *href*.
|
|---|
| | |
|
|---|
| | | There are two possible workarounds for this issue. In `gitblit.properties` or `web.xml`:
|
|---|
| | |
|
|---|
| | |
|---|
| | |
|
|---|
| | | You must ensure that the proxy does not decode and then re-encode request urls with interpretation of forward-slashes (*%2F*). If your proxy layer does re-encode embedded forward-slashes then you may not be able to browse grouped repositories or logs, branches, and tags **unless** you set *web.mountParameters=false*.
|
|---|
| | |
|
|---|
| | | If you are using Apache mod_proxy, specify [AllowEncodedSlashes NoDecode](http://httpd.apache.org/docs/2.2/mod/core.html#allowencodedslashes).
|
|---|
| | | If you are using Apache mod_proxy you may have luck with specifying [AllowEncodedSlashes NoDecode](http://httpd.apache.org/docs/2.2/mod/core.html#allowencodedslashes).
|
|---|
| | |
|
|---|
| | | ### Running Gitblit on Tomcat
|
|---|
| | |
|
|---|
| | |
|---|
| | | You have a few options on how to handle this scenario:
|
|---|
| | |
|
|---|
| | | 1. [Tweak Tomcat](http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.10)
|
|---|
| | | Add *org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true* to *CATALINA_OPTS*
|
|---|
| | | Add *-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true* to *CATALINA_OPTS* or to your JVM launch parameters
|
|---|
| | | 2. *web.mountParameters = false* and use non-pretty, parameterized urls
|
|---|
| | | 3. *web.forwardSlashCharacter = !* which tells Gitblit to use **!** instead of **/**
|
|---|
| | |
|
|---|
| | | #### UTF-8 Filenames
|
|---|
| | |
|
|---|
| | | Tomcat also dislikes urls with non-ASCII characters. If your repositories have non-ASCII filenames you will have to modify your connector properties to allow UTF-8 encoded urls. |
|---|
| | |
|
|---|
| | | [Tomcat Character Encoding](http://wiki.apache.org/tomcat/FAQ/CharacterEncoding) |
|---|
| | | [Tomcat Connector Properties](http://tomcat.apache.org/tomcat-6.0-doc/config/http.html)
|
|---|
| | |
|
|---|
| | | ## General Interest Questions
|
|---|
| | |
|
|---|
| | |
|---|
| | | **NOTE:**
|
|---|
| | | Care must be taken to preserve the relationship between user roles and repository names.<br/>Please see the *User Roles* section of the [setup](/setup.html) page for details.
|
|---|
| | |
|
|---|
| | | ### Can I restrict access to paths within a repository?
|
|---|
| | | No. Access restrictions apply to the repository as a whole.
|
|---|
| | | ### Can I restrict access to branches or paths within a repository?
|
|---|
| | | No, not out-of-the-box. Access restrictions apply to the repository as a whole.
|
|---|
| | |
|
|---|
| | | Gitblit's simple authentication and authorization mechanism can be used to facilitate one or more of the [workflows outlined here](http://progit.org/book/ch5-1.html). Should you require more fine-grained access controls you might consider using [gitolite](https://github.com/sitaramc/gitolite).
|
|---|
| | | Gitblit's simple authentication and authorization mechanism can be used to facilitate one or more of the [workflows outlined here](http://progit.org/book/ch5-1.html).
|
|---|
| | |
|
|---|
| | | Should you require more fine-grained access controls you might consider writing a Groovy *prereceive* script to block updating branch refs based on some permissions file. I would be interested in a generic, re-usable script to include with Gitblit, should someone want to implement it.
|
|---|
| | |
|
|---|
| | | Alternatively, you could use [gitolite](https://github.com/sitaramc/gitolite) and SSH for your repository access.
|
|---|
| | |
|
|---|
| | | ### Can I authenticate users against XYZ?
|
|---|
| | | Yes. The user service is pluggable. You may write your own user service by implementing the *com.gitblit.IUserService* interface. Set the fully qualified classname as the *realm.userService* property.
|
|---|
| | | Yes. The user service is pluggable. You may write your own complete user service by implementing the *com.gitblit.IUserService* interface. Or you may subclass *com.gitblit.GitblitUserService* and override just the authentication. Set the fully qualified classname as the *realm.userService* property.
|
|---|
| | |
|
|---|
| | | ### Why doesn't Gitblit support SSH?
|
|---|
| | | Gitblit could integrate [Apache Mina][mina] to provide SSH access. However, doing so violates Gitblit's first design principle: [KISS](http://en.wikipedia.org/wiki/KISS_principle).<br/>
|
|---|
| | |
|---|
| | | You might consider running [Gerrit](http://gerrit.googlecode.org) which does integrate [Apache Mina][mina] and supports SSH or you might consider serving [Git][git] on Linux which would offer real SSH support and also allow use of [many other compelling Git solutions](https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools).
|
|---|
| | |
|
|---|
| | | ### What types of Search does Gitblit support?
|
|---|
| | | Gitblit supports case-insensitive searches of *commit message* (default), *author*, and *committer*.<br/>
|
|---|
| | |
|
|---|
| | | As of 0.9.0, Gitblit supports Lucene-based searching.
|
|---|
| | |
|
|---|
| | | If Lucene indexing is disabled, Gitblit falls back to brute-force commit-traversal search. Commit-traversal search supports case-insensitive searching of *commit message* (default), *author*, and *committer*.<br/>
|
|---|
| | |
|
|---|
| | | To search by *author* or *committer* use the following syntax in the search box:
|
|---|
| | |
|
|---|
