ansaurus

Question

How can I give multiple users access to 1 git repo?

Answer 1

+1 A:

Have you considered using gitosis ?

I am not sure what you are doing here but typically, you create a user account say git and create your central repo at /home/git/project/ and add everyone you wish to give permission's public keys added to ~git/.ssh/authorized_keys After that git clone git@server:project.git should get everything working.

anshul 2010-02-12 01:33:04

Or gitolite: http://github.com/sitaramc/gitolite

Jakub Narębski 2010-02-12 13:08:40

Answer 2

A:

Are you looking for an absolute path?

[email protected]:/home/yourusername/projectname.git

phunehehe 2010-02-12 01:33:45

Nope, never even thought of doing that. Thank you for the information, I'll try this tomorrow. I'm guessing I would just add each user to a group, then give that group read/write permissions to the folder?

Ryan Kearney 2010-02-12 03:07:14

yeah I guess so :)

phunehehe 2010-02-13 01:44:54

Answer 3

A:

The key idea in git is that every user has his/her own repository. The concept of a "central" repository for everyone does not apply in the same sense as with Subversion or CVS. Instead, they are all just peers, and if you'd like to get changes someone made to their repository, you could pull the changes from them, similar, but not identical, to "updating" with SVN or CVS. You can, of course, have an "authoritative" repository that everyone can then clone from. Maybe you should read up on the idea behind distributed version control systems and decide, if you really want to use one.

An introduction for SVN users can be found here: IBM Developerworks

Daniel Schneller 2010-02-12 01:36:16

Thanks for the input but we're using git for our 5 month class project. We all have an equal amount of authority in the project so no one user would handle a master repository. The idea was we would all connect to one central repository and commit as necessary. SVN is out of the question, it's just awful.

Ryan Kearney 2010-02-12 03:04:35

@Ryan - SVN is demonstrably not awful, no issue with it not being an option in this case but equally you aren't currently able to get git to do what you want... if you want to use DVCS then you each have your own "working" repository - that's why its Distributed - and coordinate by pulling and pushing between repositories as changes are made. You will probably make your lives easier if you have a central repository that you all push changes to - not "owned" by any one member of your team but shared.

Murph 2010-02-12 08:24:43

Answer 4

A:

Read chapters "Git on the Server" and "Distributed Git" of a free Pro Git book.

Jakub Narębski 2010-02-12 13:14:01

ansaurus

tags:

views:

answers:

How can I give multiple users access to 1 git repo?

related questions