Le 2012-10-08 à 16:47, Roger Perryman <[email protected]> a écrit :

> 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.

You can either have a central repository, or each member of the group simply 
send commits/tags to the other team members. But if users are not the same 
network and don't have static IPs, will be easier to have a central repository.

> 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 -- ???

HTTP can be read/write. I prefer SSH since it use SSH keys so it will not ask 
user/pass every time with the command-line client.

If you have contributors that should only login for Git and nothing else (e.g., 
you don't want to create a real user account for them), you can use Gitolite to 
have "virtual" repositories (that is, the users will only be for Git, similar 
to what many FTP servers does).

> 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/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/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to