Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
  • 2 commits
  • 2 files changed
  • 0 commit comments
  • 1 contributor
Commits on Mar 27, 2013
@sitaramc rolename warning was in the wrong place in the section hierarchy
thanks to Sevein for catching it

(also added TOC; the page is big enough now and has enough sections)
184d4e6
@sitaramc (minor) gitlab no longer uses gitolite 09cf270
Showing with 25 additions and 28 deletions.
  1. +12 −17 why.mkd
  2. +13 −11 wild.mkd
View
29 why.mkd
@@ -87,27 +87,22 @@ annotated tags, nor does it check author/committer identity. However, it is
trivial to add your own code to do either (or if someone contributes it, to
just "enable" what ships with gitolite in a disabled state).
-### gitorious
+### gitorious and others
Anecdotally, gitorious is very hard to install. Comparison with gitolite may
be useless because I believe it doesn't have branch/tag level access control.
However, I can't confirm or deny this because I can't find any documentation
-on the website.
+on the website. In addition, the main website hides the source code very
+well, so you already have a challenge! [The only link I could find was tucked
+away at the bottom of the About page, in the License section].
-In addition, the main website hides the source code very well, so you already
-have a challenge! [The only link I could find was tucked away at the bottom
-of the About page, in the License section].
+Gitorious has several, much newer, competitors offering web-based management,
+issue tracker, wiki, and so on; try googling for gitlab, gitblit, and
+rhodecode.
-### gitlab
+However, to the best of my knowledge none of them offer branch level access
+controls (please tell me if you know different), which, since it is the main
+reason I wrote gitolite, makes them all somewhat moot.
-Gitlab is built on top of gitolite, but it does not allow branch-level access
-control which pretty much defeats the purpose of their switching from gitosis
-to gitolite if you ask me.
-
-If you like web-based management, issue tracker, wiki, and so on, you might
-like it.
-
-### others
-
-Please send in patches to this doc if you know of other open source git
-hosting solutions that do access control.
+They are also unlikely to be as [customisable][cust] as gitolite is, if you
+care about that sort of thing.
View
24 wild.mkd
@@ -1,5 +1,7 @@
# "wild" repos (user created repos)
+TOC
+
## quick introduction
The wildrepos feature allows you to specify access control rules using regular
@@ -132,6 +134,17 @@ You can add the new names to the ROLES hash in the `~/.gitolite.rc` file; see
comments in that file for how to do that. Be sure to run the 2 commands
mentioned there after you have added the roles.
+#### #rolenamewarn <font color="red">**IMPORTANT WARNING ABOUT THIS FEATURE**</font>
+
+Please make sure that none of the role names conflict with any of the user
+names or group names in the system. For example, if you have a user called
+"foo" or a group called "@foo", make sure you do not include "foo" as a valid
+role in the ROLES hash.
+
+You can keep things sane by using UPPERCASE names for roles, while keeping all
+your user and group names lowercase; then you don't have to worry about this
+problem.
+
### setting default roles
You can setup some default role assignments as soon as a new wild repo is
@@ -159,17 +172,6 @@ affects newly created wild repos, despite the '@all' name).
See the section on `OWNER_ROLENAME` in the [rc file documentation][rc].
-#### #rolenamewarn <font color="red">**IMPORTANT WARNING ABOUT THIS FEATURE**</font>
-
-Please make sure that none of the role names conflict with any of the user
-names or group names in the system. For example, if you have a user called
-"foo" or a group called "@foo", make sure you do not include "foo" as a valid
-role in the ROLES hash.
-
-You can keep things sane by using UPPERCASE names for roles, while keeping all
-your user and group names lowercase; then you don't have to worry about this
-problem.
-
## listing wild repos
In order to see what repositories were created from a wildcard, use the 'info'

No commit comments for this range

Something went wrong with that request. Please try again.