Geek Answers Handbook

Git: how best to configure the user model on a "back-end server"

I have a very specific question about the user model. (I suppose asking this question betrays my ignorance, but hey, I just want to know!)

I have a simple Ubuntu server in which our project repository will be stored, from which about 6 guys will clone the project. Each of them has its own user account on this host. The project repository is on the path / home / git / project-name.git. I could create a group to sunbathe these users and the git user.

When developer users click on this remote repository, I don’t want them to do all this as the same user (say, the user 'git' or something else), since I want to know who did what.

If I have all the id_rsa.pub.name keys on the path / home / git / .ssh /, then add yourself to * / home / git /. ssh / authorized_keys *, without knowing who did what, right?

Therefore, do I give full access to / home / git / project-name.git for each group to which the developer accounts on this host belong?

Any advice would be warmly welcome.

Thanks Russ

+5
source share
4 answers

A common practice is to have one account, and not have multiple ssh accounts for everyone to click on a repo.

http://progit.org/book/ch4-4.html

http://blog.felipebalbi.com/2008/01/03/git-push-and-ssh-keys/

, . / ssh.

+3

, Gitosis, Gitolite ssh.

+5

- Gitolite () , , . git, Git . Git , , , .

+3

, " ".

, (-) (blob, tree, commit, ) , ( , , ), . (, git gc, , ).

Git, , , , "", push 1. , " // ". , , . , Git Git, "" , . :

(, , /).

. : Git

1 Git tracks the author and committer for each commit (tagger for each annotated tag), but their values ​​are not limited to Git. Anyone can change the effective author or committer by changing (or overriding) their configuration variables user.emailand user.nameor setting the environment variables GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL when committing or tagging.

+2
source

More articles:


All Articles