From 493ab0f0d6f60528e11d293be4cb68817c7517a5 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Sat, 12 Nov 2011 10:49:10 -0500
Subject: [PATCH] Documentation. Updated Twitter Bootstrap to 1.4.0.
---
docs/01_setup.mkd | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/01_setup.mkd b/docs/01_setup.mkd
index 42f7c0c..0939d5a 100644
--- a/docs/01_setup.mkd
+++ b/docs/01_setup.mkd
@@ -134,6 +134,7 @@
showReadme = false
federationStrategy = FEDERATE_THIS
isFederated = false
+ skipSizeCalculation = false
federationSets =
#### Repository Names
@@ -158,7 +159,7 @@
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.
@@ -177,7 +178,7 @@
* Setup the user service.
*
* @param settings
- * @since 0.6.1
+ * @since 0.7.0
*/
@Override
public void setup(IStoredSettings settings) {
--
Gitblit v1.9.1