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

dps: gl-setup may have to create ~/.ssh and touch the authkeys file...

Browse source 
I've been unwilling to create the authkeys file if it does not already
exist, because it represents a significant change in accessibility for
that account.

However, in the "distro package" scenario, one wants to make it as easy
as possible for the end-user (who is actually an admin for the gitolite
being hosted on his account, let's not forget) to use.

And it seems that in some cases that might mean he does not (yet) have a
~/.ssh even...
This commit is contained in:
Sitaram Chamarty 2010-03-12 09:04:00 +05:30
parent b3945d44c9
commit 7588c8cf54
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
src/gl-setup
View file

@ -52,6 +52,15 @@ else
cp $GL_PACKAGE_CONF/example.gitolite.rc ~/.gitolite.rc cp $GL_PACKAGE_CONF/example.gitolite.rc ~/.gitolite.rc
fi fi
# setup ssh stuff. We break our normal rule that we will not fiddle with
# authkeys etc., because in this case it seems appropriate
cd
mkdir -p .ssh
touch .ssh/authorized_keys
chmod go-w . .ssh .ssh/authorized_keys
# now we get to gitolite itself
gl-install -q gl-install -q
GL_ADMINDIR=$(cd;perl -e 'do ".gitolite.rc"; print $GL_ADMINDIR') GL_ADMINDIR=$(cd;perl -e 'do ".gitolite.rc"; print $GL_ADMINDIR')