| | |
|---|
| | | 2. Confirm that the servlet container process has full read-write-execute permissions to your *git.repositoriesFolder*.
|
|---|
| | |
|
|---|
| | | ### Gitblit WAR will not authenticate any users?!
|
|---|
| | | Confirm that the <context-param> *realm.userService* value in your `web.xml` file actually points to a `users.properties` file.
|
|---|
| | | Confirm that the <context-param> *realm.userService* value in your `web.xml` file actually points to a `users.conf` or `users.properties` file.
|
|---|
| | |
|
|---|
| | | ### Gitblit won't open my grouped repository (/group/myrepo.git) or browse my log/branch/tag/ref?!
|
|---|
| | | This is likely an url encoding/decoding problem with forward slashes:
|
|---|
| | |
|---|
| | | Gitblit will run just fine with a JRE. Gitblit can optionally use `keytool` from the JDK to generate self-signed certificates, but normally Gitblit uses [BouncyCastle][bouncycastle] for that need.
|
|---|
| | |
|
|---|
| | | ### Does Gitblit use a database to store its data?
|
|---|
| | | No. Gitblit stores its repository configuration information within the `.git/config` file and its user information in `users.properties` or whatever filename is configured in `gitblit.properties`.
|
|---|
| | | No. Gitblit stores its repository configuration information within the `.git/config` file and its user information in `users.conf`, `users.properties`, or whatever filename is configured in `gitblit.properties`.
|
|---|
| | |
|
|---|
| | | ### Can I manually edit users.properties, gitblit.properties, or .git/config?
|
|---|
| | | ### Can I manually edit users.conf, users.properties, gitblit.properties, or .git/config?
|
|---|
| | | Yes. You can manually manipulate all of them and (most) changes will be immediately available to Gitblit.<br/>Exceptions to this are noted in `gitblit.properties`.
|
|---|
| | |
|
|---|
| | | **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/>
|
|---|
