| | |
|---|
| | | - RSS/JSON RPC interface
|
|---|
| | | - Java/Swing Gitblit Manager tool
|
|---|
| | | - Gitweb inspired web UI
|
|---|
| | | - Groovy pre- and post- push hook scripts, per-repository or globally for all repositories
|
|---|
| | | - Administrators may create, edit, rename, or delete repositories through the web UI or RPC interface
|
|---|
| | | - Administrators may create, edit, rename, or delete users through the web UI or RPC interface
|
|---|
| | | - Administrators may create, edit, rename, or delete teams through the web UI or RPC interface
|
|---|
| | |
|---|
| | |
|
|---|
| | | ## Limitations
|
|---|
| | | - HTTP/HTTPS are the only supported Git protocols
|
|---|
| | | - Access controls are not path-based, they are repository-based
|
|---|
| | | - Built-in access controls are not path-based, they are repository-based. |
|---|
| | | - Only Administrators can create, rename or delete repositories
|
|---|
| | | - Only Administrators can create, modify or delete users
|
|---|
| | | - Commit hooks are not supported
|
|---|
| | | - Only Administrators can create, modify or delete teams
|
|---|
| | | - Native Git may be needed to periodically run git-gc as [JGit][jgit] does not fully support the git-gc featureset.
|
|---|
| | |
|
|---|
| | | ### Caveats
|
|---|
