| | |
|---|
| | | 2. The server itself is configured through a simple text file.
|
|---|
| | | Open `data/gitblit.properties` in your favorite text editor and make sure to review and set:
|
|---|
| | | - *server.httpPort* and *server.httpsPort*
|
|---|
| | | - *server.storePassword*
|
|---|
| | | - *server.storePassword* (do not enter *#* characters)
|
|---|
| | | **https** is strongly recommended because passwords are insecurely transmitted form your browser/git client using Basic authentication!
|
|---|
| | | - *git.packedGitLimit* (set larger than the size of your largest repository)
|
|---|
| | | - *git.streamFileThreshold* (set larger than the size of your largest committed file)
|
|---|
| | | 3. Execute `authority.cmd` or `java -cp gitblit.jar com.gitblit.authority.Launcher --baseFolder data` from a command-line
|
|---|
| | | **NOTE:** The Authority is a Swing GUI application. Use of this tool is not required as Gitblit GO will startup and create SSL certificates itself, BUT use of this tool allows you to control the identification metadata used in the generated certificates. Skipping this step will result in certificates with default metadata.
|
|---|
| | | 1. fill out the fields in the *new certificate defaults* dialog
|
|---|
| | |
|---|
| | |
|
|---|
| | | If you want to serve your repositories to another machine over https then you will want to generate a new certificate for the hostname or ip address you are serving from.
|
|---|
| | |
|
|---|
| | | **NOTE:** The Gitblit Authority is a GUI tool and will require X11 forwarding on headless UNIX boxes.
|
|---|
| | |
|
|---|
| | | 1. `authority.cmd` or `java -jar authority.jar --baseFolder data`
|
|---|
| | | 2. Click the *new ssl certificate* button (red rosette in the toolbar in upper left of window)
|
|---|
| | | 3. Enter the hostname or ip address
|
|---|
