Code your own Multi-User Private Git Server
moocode.com
Code your own Multi-User Private Git Server
1–10 of 18 posts
Re: Code your own Multi-User Private Git Server
#2Copying code into a file isn't 'coding'. And it took a lot more than 5 minutes to work all this out.
Re: Code your own Multi-User Private Git Server
#3Copying code into a file isn't 'coding'. And it took a lot more than 5 minutes to work all this out.
Sorry if you find the title misleading, it certainly wasn't intended that way. In fact, sometimes I find it harder to pick the right title than I do to write the blog post.
My intentions were that you could read the article in 5 minutes and the code sample would give you a good starting point to code your own implementation.
Re: Code your own Multi-User Private Git Server
#4I use gitosis, and it's very simple to set up and manage. It doesn't feel like overkill at all.
Re: Code your own Multi-User Private Git Server
#5I use gitosis, and it's very simple to set up and manage. It doesn't feel like overkill at all.
I like Gitolite, it has more fine grained permission control and is pretty simple to get up and running.
Re: Code your own Multi-User Private Git Server
#6This 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.
Re: Code your own Multi-User Private Git Server
#7Don't see why it was necessary to criticize the post so much. True, the title is a bit inadequate, but it's nice to find a combination of several tidbits, tips and tricks combined on one page.
Re: Code your own Multi-User Private Git Server
#8This 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.
Agreed. Or for small trusted teams any linux box with ssh access will do fine. This is a very well served product area, it really shouldn't be a problem that demands new software development.
Edit: Hah! That's basically what it is, just dressed up with a tiny script and the two-factor trick from last week. Never mind then. This is sane. Just maybe oversold.
Re: Code your own Multi-User Private Git Server
#9This 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 give the reader the tools they need to roll their own solution if they want.
Re: Code your own Multi-User Private Git Server
#10Don't see why it was necessary to criticize the post so much. True, the title is a bit inadequate, but it's nice to find a combination of several tidbits, tips and tricks combined on one page.
Thanks, I don't understand the criticism either, the feedback via twitter has been quite positive so I will take both on board when writing any further posts.