| | |
| | | - <context-parameter> *realm.userService* (set the full path to `users.properties`)
|
| | | 5. You may have to restart your servlet container.
|
| | | 6. Open your browser to <http://localhost/gitblit> or whatever the url should be.
|
| | | 7. Click the *Login* link and enter the default administrator credentials: **admin / admin** |
| | | 7. Enter the default administrator credentials: **admin / admin** and click the *Login* button |
| | | **NOTE:** Make sure to change the administrator username and/or password!!
|
| | |
|
| | | ## Gitblit GO Setup
|
| | |
| | | 4. Wait a minute or two while all dependencies are downloaded and your self-signed *localhost* certificate is generated.
|
| | | Please see the section titled **Creating your own Self-Signed Certificate** to generate a certificate for *your hostname*.
|
| | | 5. Open your browser to <http://localhost:8080> or <https://localhost:8443> depending on your chosen configuration.
|
| | | 6. Click the *Login* link and enter the default administrator credentials: **admin / admin** |
| | | 6. Enter the default administrator credentials: **admin / admin** and click the *Login* button |
| | | **NOTE:** Make sure to change the administrator username and/or password!!
|
| | |
|
| | | ### Creating your own Self-Signed Certificate
|
| | |
| | | showReadme = false
|
| | | federationStrategy = FEDERATE_THIS
|
| | | isFederated = false
|
| | | skipSizeCalculation = false
|
| | | federationSets =
|
| | |
|
| | | #### Repository Names
|
| | |
| | | Whitespace is illegal.
|
| | |
|
| | | #### Passwords
|
| | | User passwords are CASE-SENSITIVE and may be *plain* or *md5* formatted (see `gitblit.properties` -> *realm.passwordStorage*).
|
| | | User passwords are CASE-SENSITIVE and may be *plain*, *md5*, or *combined-md5* formatted (see `gitblit.properties` -> *realm.passwordStorage*).
|
| | |
|
| | | #### User Roles
|
| | | There are two actual *roles* in Gitblit: *#admin*, which grants administrative powers to that user, and *#notfederated*, which prevents an account from being pulled by another Gitblit instance. 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.
|
| | |
| | | * Setup the user service.
|
| | | *
|
| | | * @param settings
|
| | | * @since 0.6.1
|
| | | * @since 0.7.0
|
| | | */
|
| | | @Override
|
| | | public void setup(IStoredSettings settings) {
|