| | |
|---|
| | | ## Gitblit Features
|
|---|
| | | ## Standard Features (GO/WAR)
|
|---|
| | | - JGit SmartHTTP servlet
|
|---|
| | | - Browser and git client authentication
|
|---|
| | | - Four *per-repository* access control configurations with a Read-Only control flag
|
|---|
| | |
|---|
| | | - Gitweb inspired web UI
|
|---|
| | | - 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
|
|---|
| | | - Repository Owners may edit repositories through the web UI
|
|---|
| | | - Git-notes display support
|
|---|
| | | - Branch metrics (uses Google Charts)
|
|---|
| | |
|---|
| | | - A Windows service installation script and configuration tool
|
|---|
| | |
|
|---|
| | | ## Limitations
|
|---|
| | | - HTTP/HTTPS are the only supported protocols
|
|---|
| | | - HTTP/HTTPS are the only supported Git protocols
|
|---|
| | | - 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
|
|---|
