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

towel needed more clarity

Browse source 
for people who don't get the continual reference to towels when talking
about the "gl-dont-panic" program, all I can say is that your education
is incomplete ;-)
This commit is contained in:
Sitaram Chamarty 2010-09-09 06:52:32 +05:30
parent 2349afdc78
commit 37a6a6a7d3
1 changed files with 12 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
src/gl-dont-panic
View file

@ -19,13 +19,21 @@ usage() {
- (FIX #1: REWINDING BAD ADMIN COMMITS) if your last commit(s) to the - (FIX #1: REWINDING BAD ADMIN COMMITS) if your last commit(s) to the
gitolite-admin repo pushed a very bad config and you want to rewind it gitolite-admin repo pushed a very bad config and you want to rewind it
to a known good state, run this: to a known good state, run this:
./gl-dont-panic rewind
$0 rewind
(this doesn't actually rewind; it creates a new commit that has (this doesn't actually rewind; it creates a new commit that has
the same state as the last good commit, which has the same effect) the same state as the last good commit, which has the same effect)
- (FIX #2: PUSHING A NEW ADMIN KEY) if you lost your admin key, run this - (FIX #2: PUSHING A NEW ADMIN KEY) if you lost your admin key, or you
with the new pubkey: had used the wrong key initially, then you get yourself a new keypair
./gl-dont-panic sitaram.pub and run this with the new pubkey:
$0 sitaram.pub # example using my name
Please note that this simply *replaces* the key for user "sitaram".
It does NOT add a new admin called "sitaram". In fact it does not
touch the config file (access rules) at all.
Step 3: completing the fix (on your workstation) Step 3: completing the fix (on your workstation)