You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/00_index.mkd
+5-5
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
Git:Blit is an open-source, integrated pure Java stack for managing, viewing, and serving [Git][git] repositories.
3
3
Its designed primarily as a tool for small workgroups who want to host [Git][git] repositories on a Windows machine. Having said that, it works equally well on any standard Linux distribution.
4
4
5
-
### Current Version
5
+
### Current Release
6
6
7
7
[%VERSION%](http://gitblit.com/%DISTRIBUTION%) based on [%JGIT%][jgit] (*%BUILDDATE%*)
8
8
@@ -27,11 +27,12 @@ sources @ [Github][gitbltsrc]
27
27
</ul>
28
28
- Gitweb inspired UI
29
29
- Administrators may create, edit, rename, or delete repositories through the web UI
30
-
- Administrators may create, edit, or delete users through the web UI
30
+
- Administrators may create, edit, rename, or delete users through the web UI
31
31
- Repository Owners may edit repositories through the web UI
32
32
- Automatically generates a self-signed certificate for https communications
33
-
- Dates can optionally be displayed using the browser''s reported timezone
33
+
- Dates can optionally be displayed using the browser's reported timezone
34
34
- Author and Committer email address display can be controlled
35
+
- Realtime zip downloads feature
35
36
- Markdown view support
36
37
- Syntax highlighting
37
38
- Customizable regular expression handling for commit messages
@@ -56,7 +57,6 @@ sources @ [Github][gitbltsrc]
56
57
- users.properties access
57
58
- available repositories
58
59
- etc
59
-
- Download zip feature
60
60
- Site documentation
61
61
- Code documentation
62
62
- Unit testing
@@ -68,7 +68,7 @@ sources @ [Github][gitbltsrc]
68
68
- View images on Blob page
69
69
- View other binary files on Blob page
70
70
- Markdown editing feature
71
-
- Blame feature (waiting for the [JGit][jgit] team to do the hard part)
71
+
- Blame (waiting for the [JGit][jgit] team to do the hard part)
Copy file name to clipboardExpand all lines: docs/00_setup.mkd
+1-1
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ Usernames must be unique and are case-insensitive.<br/>
48
48
Whitespace is illegal.
49
49
50
50
#### Passwords
51
-
User passwords are CASE-SENSITIVE and may be *plain*, *md5*, or *crypt* formatted (see `gitblit.properties` -> *realm.passwordStorage*).
51
+
User passwords are CASE-SENSITIVE and may be *plain*or *md5* formatted (see `gitblit.properties` -> *realm.passwordStorage*).
52
52
53
53
#### User Roles
54
54
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.
Copy file name to clipboardExpand all lines: docs/01_faq.mkd
+7-2
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,14 @@ No. Git:Blit stores its repository configuration information within the `.git/c
16
16
### I want to deploy Git:Blit into my own servlet container. Where is the WAR?
17
17
At this time there is no WAR build available.
18
18
19
+
### Can I restrict access to paths within a repository?
20
+
No. Access restrictions apply to the repository as a whole.
21
+
22
+
Git:Blit's simple authentication and authorization mechanism can be used to facilitate one or more of the [workflows outlined here](http://progit.org/book/ch5-1.html). Should you require more fine-grained access controls you might consider using [gitolite](https://github.com/sitaramc/gitolite).
23
+
19
24
### Why doesn't Git:Blit support SSH?
20
25
Git:Blit could integrate [Apache Mina][mina] to provide SSH access. However, doing so violates Git:Blit's first design principle: [KISS](http://en.wikipedia.org/wiki/KISS_principle).<br/>
21
-
SSH supports requires creating, exchanging, and managing SSH keys. While this is doable, its not simple like JGit's SmartHTTP implementation.
26
+
SSH support requires creating, exchanging, and managing SSH keys. While this is possible, JGit's SmartHTTP implementation is a simpler and cleaner transport mechanism.
22
27
23
28
You might consider running [Gerrit](http://gerrit.googlecode.org) which does integrate [Apache Mina][mina] and supports SSH or you might consider serving [Git][git] on Linux which would offer real SSH support and also allow use of [many other compelling Git solutions](https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools).
24
29
@@ -34,7 +39,7 @@ Alternatively, you could enable the search type dropdown list in your `gitblit.p
34
39
35
40
### How do I run Git:Blit on port 80 or 443 in Linux?
36
41
Linux requires root permissions to serve on ports < 1024.<br/>
37
-
Run the server as *root* (security concern) or change the ports you are serving to 8080 (http) or 8443 (https).
42
+
Run the server as *root* (security concern) or change the ports you are serving to 8080 (http) and/or 8443 (https).
0 commit comments