deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

docs: document how to specify "owner" for gitweb

Browse source
This commit is contained in:
Sitaram Chamarty 2009-11-27 13:47:21 +05:30
parent d2a053ba3c
commit d8cb62934f
4 changed files with 17 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.mkd
View file

@ -73,7 +73,7 @@ detail [here][gsdiff].
* config file syntax gets checked upfront, and much more thoroughly * config file syntax gets checked upfront, and much more thoroughly
* if your requirements are still too complex, you can split up the config * if your requirements are still too complex, you can split up the config
file and delegate authority over parts of it file and delegate authority over parts of it
* easier to specify gitweb "description" and gitweb/daemon access * easier to specify gitweb owner, description and gitweb/daemon access
* easier to sync gitweb (http) authorisation with gitolite's access config * easier to sync gitweb (http) authorisation with gitolite's access config
* more comprehensive logging [aka: management does not think "blame" is just * more comprehensive logging [aka: management does not think "blame" is just
a synonym for "annotate" :-)] a synonym for "annotate" :-)]

8
conf/example.conf
View file

@ -130,13 +130,13 @@ repo @oss_repos
repo linux perl repo linux perl
R = gitweb R = gitweb
# GITWEB DESCRIPTION LINE # REPO OWNER/DESCRIPTION LINE FOR GITWEB
# syntax: # syntax, one of:
# reponame = "some description string in double quotes" # reponame = "some description string in double quotes"
# reponame "owner name" = "some description string in double quotes"
# note: setting a description also gives gitweb access; you do not have to # note: setting a description also gives gitweb access; you do not have to
# give gitweb access as described above if you're specifying a description # give gitweb access as described above if you're specifying a description
gitolite = "fast, secure, access control for git in a corporate environment" gitolite "Sitaram Chamarty" = "fast, secure, access control for git in a corporate environment"

11
doc/2-admin.mkd
View file

@ -57,13 +57,18 @@ so you may as well use that method and kill two birds with one stone, like so:
gitolite = "fast, secure, access control for git in a corporate environment" gitolite = "fast, secure, access control for git in a corporate environment"
You can also specify an owner for gitweb to show, if you like:
gitolite "Sitaram Chamarty" = "fast, secure, access control for git in a corporate environment"
Note that gitolite does **not** install or configure gitweb/daemon -- that is Note that gitolite does **not** install or configure gitweb/daemon -- that is
a one-time setup you must do separately. All this does is: a one-time setup you must do separately. All this does is:
* for daemon, create the file `git-daemon-export-ok` in the repository * for daemon, create the file `git-daemon-export-ok` in the repository
* for gitweb, add the repo to the list of projects to be served by gitweb * for gitweb, add the repo (plus owner name, if given) to the list of
(see the config file variable `$PROJECTS_LIST`, which should have the same projects to be served by gitweb (see the config file variable
value you specified for `$projects_list` when setting up gitweb) `$PROJECTS_LIST`, which should have the same value you specified for
`$projects_list` when setting up gitweb)
* put the description, if given, in `$repo/description` * put the description, if given, in `$repo/description`
The "compile" script will keep these files consistent with the config settings The "compile" script will keep these files consistent with the config settings

4
doc/3-faq-tips-etc.mkd
View file

@ -204,6 +204,10 @@ file:
reponame = "one line of description" reponame = "one line of description"
You can also specify an "owner":
reponame "owner name" = "one line of description"
To enable access to one or more repos via git daemon, just give "read" To enable access to one or more repos via git daemon, just give "read"
permissions to the special username `daemon`. permissions to the special username `daemon`.