I wrote:
> It depends on how fine-grained you want things. If all the users have
> ssh accounts on the system, you can just make the repository shared
> and add everyone who should have commit privileges to the group used
> for the repository. This is how it is done on fedorahosted.org. For
> example, if your git repo is at /git/repo.git:
>
> # Tell git the repository is shared
> $ git --git-dir /git/repo.git config core.sharedrepository true
>
> # Set proper group ownership
> $ chgrp -R gitgroup /git/repo.git
>
> # Make all directories setgid
> $ find /git/repo.git -type d -exec chmod g+s {} \;
>
> # Ensure files and dirs are group writable
> $ find /git/repo.git/ \( -type f -o -type d \) -a \
> \( -perm /u+w -a ! -perm /g+w \) \
> xargs chmod g+w
Incidentally, most of this is only needed if you're dealing with a
repository that you've already created. If you're initializing a new
repo you can skip most of it.
$ git --git-dir /git/repo.git --bare init --shared=true
$ chgrp -R gitgroup /git/repo.git
Then you can easily push things into it from an existing repo to add
content and git will handle the permissions.
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Nothing is wrong with California that a rise in the ocean level
wouldn't cure.
-- Ross MacDonald (1915-1983)
Attachment:
pgp6GbJpc53Gg.pgp
Description: PGP signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
