334360092d
* Improve MESSAGE
Changelog:
2014-06-22 v3.6.1 experimental rc format convertor for "<= 3.3" users who
have already upgraded the *code* to ">= v3.4". Program is
in contrib/utils.
giving shell access to a few users got a lot easier (see
comments in the rc file).
allow logging to syslog as well (see comments in the rc
file)
new 'motd' command
redis caching redone and now in core; see
http://gitolite.com/gitolite/cache.html
2014-05-09 v3.6 (cool stuff) the access command can now help you debug
your rules / understand how a specific access decision was
arrived at.
mirroring: since mirroring is asynchronous (by default
anyway), when a 'git push --mirror' fails, you may not
know it unless you look in the log file on the server.
Now gitolite captures the info and -- if the word 'fatal'
appears anywhere within it, it saves the entire output and
prints it to STDERR for anyone who reads or writes the
repo on the *master* server, until the error condition
clears up.
mirroring: allow 'nosync' slaves -- no attempt to
automatically push to these slaves will be made. Instead,
you have to manually (or via cron, etc) trigger pushes.
(backward compat breakage) the old v2 syntax for
specifying gitweb owner and description is no longer
supported.
macros now allow strings as arguments (thanks to Jason
Donenfeld for the idea/problem).
the 'info' command can print in JSON format if asked to.
repo-specific hooks: now you can specify more than one,
and gitolite runs all of them in sequence.
new trigger 'expand-deny-messages' to show more details
when access is denied.
git-annex support is finally in master, yaaay!
new 'readme' command, modelled after 'desc'. Apparently
gitweb can use a README.html file in the *bare* repo
directory -- who knew!
2013-10-14 v3.5.3 catch undefined groupnames (when possible)
mirroring: async push to slaves
(some portability fixes)
(a couple of contrib scripts - querying IPA based LDAP
servers for group membership, and user key management)
allow groups in subconf files (this *may* slow down
compilation in extreme cases)
make adding repo-specific hooks easier (see cust.mkd or
cust.html online for docs)
smart http now supports git 1.8.2 and above (which changed
the protocol requirements a wee bit)
47 lines
1.1 KiB
Text
47 lines
1.1 KiB
Text
===========================================================================
|
|
$NetBSD: MESSAGE,v 1.4 2014/07/12 04:56:09 ryoon Exp $
|
|
|
|
To use gitolite, you will need to perform the following steps.
|
|
|
|
1. Create a new user/group, for example, git/git.
|
|
|
|
On server,
|
|
# groupadd git
|
|
# useradd -m -g git git
|
|
|
|
2. login with new user git, create ssh public key, and copy public key
|
|
file to user git's home directory on server.
|
|
|
|
On server
|
|
$ mkdir ~/.ssh
|
|
$ chmod 700 ~/.ssh
|
|
|
|
On client
|
|
$ ssh-keygen -t rsa -f git
|
|
$ scp ~/git.pub gitserver:~/
|
|
|
|
On server
|
|
$ chmod 600 ~/git.pub
|
|
|
|
3. Setup gitolite.
|
|
|
|
On server, run
|
|
$ gitolite setup -pk git.pub
|
|
|
|
You can get gitolite-admin.git and testing.git repositories.
|
|
And edit config file.
|
|
|
|
4. Setup ~/.ssh/config on client.
|
|
Add the following lines.
|
|
|
|
host gitserver
|
|
user git
|
|
hostname RealGitServerName
|
|
port 22
|
|
identityfile ~/.ssh/git
|
|
|
|
5. For administrative setting, please clone gitolite-admin repository.
|
|
|
|
On client,
|
|
$ git clone gitserver:gitolite-admin
|
|
===========================================================================
|