11–18 of 18 posts
What's important to note is that this also talks about SSH_ORIGINAL_COMMAND, which is the environment variable set by sshd when invoking the forced command that is specified in authorized_keys.
Clever hack.
This just seems to be a case of Not Invented Here syndrome. Using gitolite or gitosis would have done the job faster, gives you the ability to have acl's set up per user and all of it uses simple configuration files.
To be fair, the example I have given is simple and you could use something like gitosis or gitolite (I have used them in the past). The point of the article was supposed to be a starting point if you have something else you want to do. For example, I needed to have a fully distributed git backend system across multiple git storage nodes so I needed to learn how I would go about doing that. This post was supposed to g…
I use gitosis, and it's very simple to set up and manage. It doesn't feel like overkill at all.
I use gitosis, and it's very simple to set up and manage. It doesn't feel like overkill at all.
I was using Gitosis, now i switch to Gitolite, it's better and simpler.
This just seems to be a case of Not Invented Here syndrome. Using gitolite or gitosis would have done the job faster, gives you the ability to have acl's set up per user and all of it uses simple configuration files.
Gitolite is a great project and it has many useful features such as branch-level access control. That might be what he meant by "overkill". He simply didn't need those features. I think there's much to be said for keeping things simple.
root@server# apt-get install git-core
git@server$ mkdir ~git/repo.git
git@server$ git init $!
user@client$ git remote add origin ssh://git@server/repo.git