| | |
|---|
| | | ## Setup and Configuration
|
|---|
| | |
|
|---|
| | | 1. Download and unzip Git:Blit.<br/>
|
|---|
| | | 1. Download and unzip [%VERSION%](http://gitblit.com/%DISTRIBUTION%).<br/>
|
|---|
| | | *Its best to eliminate spaces in the path name as that can cause troubleshooting headaches.*
|
|---|
| | | 2. The server itself is configured through a simple text file.<br/>
|
|---|
| | | Open `gitblit.properties` in your favorite text editor and make sure to review and set:
|
|---|
| | |
|---|
| | | Whitespace is illegal.
|
|---|
| | |
|
|---|
| | | #### Passwords
|
|---|
| | | User passwords are CASE-SENSITIVE and may be *plain*, *md5*, or *crypt* formatted (see `gitblit.properties` -> *realm.passwordStorage*).
|
|---|
| | | User passwords are CASE-SENSITIVE and may be *plain* or *md5* formatted (see `gitblit.properties` -> *realm.passwordStorage*).
|
|---|
| | |
|
|---|
| | | #### User Roles
|
|---|
| | | There is only one actual *role* in Git:Blit and that is *#admin* which grants administrative powers to that user. Administrators automatically have access to all repositories. All other *roles* are repository names. If a repository is access-restricted, the user must have the repository's name within his/her roles to bypass the access restriction. This is how users are granted access to a restricted repository.
|
|---|
