I think gitolite is just great for a team that wants unlimited private repos, 
unlimited users and fine-grained access control on repos and branches where/if 
needed.

Expect to spend a while reading the docs the first time you install it to set 
up your repos, users and access controls. After that "it just works". It is a 
pure and simple git repo server.

https://github.com/sitaramc/gitolite

On Oct 8, 2012, at 5:56 PM, [email protected] wrote:

> 
> 
> Envoyé de mon iPhone
> 
> Le 2012-10-08 à 17:51, "Roger Perryman" <[email protected]> a écrit :
> 
>> 
>> On Oct 8, 2012, at 5:26 PM, Kieran Kelleher wrote:
>> 
>>> Hi Roger,
>>> 
>>> Here are the free solutions that I use:
> 
>>> 
>>> (1) github.com for open source projects.
>>> 
>>> (2) https://bitbucket.org/plans is ideal for small teams of 5 or less and 
>>> unlimited private repos
>>> 
>>> (3) gitolite works great on a private linux environment - it just needs a 
>>> single regular user account. Easy to install, configure and manage, 
>>> unlimited users and repos. Has some nice access controls to limit branches 
>>> and/or repos that specific users can commit to, allows per-repo 
>>> configuration. I like it and would recommend it for Linux - I have not set 
>>> it up on OS X. YMMV. Set it up and forget it. Administration is via simple 
>>> config files in a admin repo. Admin changes are performed in the local 
>>> clone of the admin report and pushed to server. So full admin change 
>>> history is also in the git history of the admin repo. Adding a user is a 
>>> simple case of adding their public ssh key to a folder.
>> 
>> If it uses a single regular user account, how does it keep track of who 
>> actually made the changes? Does it get it from the information embedded in 
>> the commit objects? If not, it would seem that I would need dedicated user 
>> accounts for each developer. A single user account seems to work for a 
>> read-only repository more than for team development.
> 
> It's a single user on the system, but it have virtual users, and each must 
> have their own SSH key, this is how it finds which user it is.
>> 
>>> HTH, Kieran
>>> 
>>> 
>>> 
>>> On Oct 8, 2012, at 4:57 PM, Ramsey Gurley <[email protected]> wrote:
>>> 
>>>> Hi Roger,
>>>> 
>>>> The thing with git is that it's just a directory. There's not really a 
>>>> server to it like SVN. As such, I ran into a lot of problems trying to get 
>>>> it to work well with multiple users because of permissions issues.  
>>>> 
>>>> For centralization, I've just used GitHub. If you really want to keep code 
>>>> on your own machines, gitosis is one way to do that, but I've never tried 
>>>> it.
>>>> 
>>>> https://wiki.archlinux.org/index.php/Gitosis
>>>> 
>>>> Ramsey
>>>> 
>>>> On Oct 8, 2012, at 1:47 PM, Roger Perryman wrote:
>>>> 
>>>>> I have some questions about how to setup a git repository for my 
>>>>> projects. I reviewed Kieran's presentation on git from WOWODC 2012. It 
>>>>> does a great job discussing git from the client's perspective but I 
>>>>> didn't see anything about setting my own repository. I realize that it is 
>>>>> distributed but I think a "central repository" can still be used. If I am 
>>>>> misunderstanding the way git works, feel free to correct me.
>>>>> 
> 
>>>>> What connection method is the best to use and what are people using?
>>>>>   SSH -- Allows tracking of individual user commits
>>>>>   HTTP -- Seems best for read-only access
>>>>>   Other -- ???
>>>>> 
>>>>> What are the pros/cons of each connection method?
>>>>> 
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Roger
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list      ([email protected])
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
>>>>> 
>>>>> This email sent to [email protected]
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list      ([email protected])
>>>> Help/Unsubscribe/Update your Subscription:
>>>> https://lists.apple.com/mailman/options/webobjects-dev/kelleherk%40gmail.com
>>>> 
>>>> This email sent to [email protected]
>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
>> 
>> This email sent to [email protected]
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/kelleherk%40gmail.com
> 
> This email sent to [email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to