2012-04-05 18:01:23 +02:00
|
|
|
# quick install, setup, and clone
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
(Please do not ignore the "assumptions" list below).
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
On the server:
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
# get the software
|
2012-04-17 03:13:13 +02:00
|
|
|
git clone git://github.com/sitaramc/gitolite
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
# install it
|
|
|
|
gitolite/install -ln
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
# setup the initial repos with your key
|
|
|
|
gitolite setup -pk your-name.pub
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
On your workstation:
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
# clone the admin repo so you can start adding stuff
|
|
|
|
git clone git@host:gitolite-admin.git
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
## ASSUMPTIONS
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-17 03:13:13 +02:00
|
|
|
* This is a fresh install, not a migration from the old gitolite (v1.x,
|
2012-04-06 10:07:30 +02:00
|
|
|
v2.x).
|
|
|
|
|
2012-04-17 03:13:13 +02:00
|
|
|
* On the server, your `$PATH` contains `$HOME/bin`. If you don't like that,
|
2012-04-05 18:01:23 +02:00
|
|
|
there are [other install methods][install].
|
|
|
|
|
|
|
|
* "your-name.pub" is your public key from your workstation.
|
2012-04-17 03:13:13 +02:00
|
|
|
* Also, this key does not already have shell access to this gitolite
|
|
|
|
hosting user.
|
2012-04-05 18:01:23 +02:00
|
|
|
|
2012-04-17 03:13:13 +02:00
|
|
|
* The setup command does not generate any warnings.
|
|
|
|
* If it does, please see [common errors][ce] and fix things before
|
2012-04-05 18:01:23 +02:00
|
|
|
continuing, or read the more complete [setup][] page.
|
|
|
|
|
|
|
|
## Notes
|
|
|
|
|
|
|
|
Note that the clone path is NOT "repositories/gitolite-admin.git". If you
|
|
|
|
clone with a path that includes "repositories/", the clone should fail. If
|
|
|
|
the clone *does* succeed, a subsequent push should fail :-) See
|
|
|
|
[this][ybpfail] for some details. If that doesn't make enough sense read all
|
|
|
|
of [ssh][].
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
## next steps
|
2012-03-16 02:54:47 +01:00
|
|
|
|
2012-04-05 18:01:23 +02:00
|
|
|
Next steps are usually adding [users][] and [repos][] and learning about
|
2012-03-16 02:54:47 +01:00
|
|
|
[access control][conf].
|