Re: Remote repository permissions best practices

[Russ Sherk]

In our location we have set up a unix group 'dev' with the proper
access permissions.  All users who will commit to cvs need to be part
of this group.

This does not prevent other users with different group from
committing.  There are some issues we have had where a user from group
'tst' have committed and messed up the access rights (file
permisssions in CVSROOT).  To solve this (asside from chgrp) we make
the user 'newgrp dev' before checking out.

Salue,

--Russ


On Mon, 28 Mar 2005 11:03:06 -0500, Howard, Les
<address@hidden> wrote:
>  
> 
> I've hacked my way through setting up a few CVS repositories in the past,
> but I've always struggled with getting the user/group ownership and file
> permissions correct.  I always seem to end up with a setup where the users
> can't access the files that other users have submitted without going into
> the repository as root and chmod/chowning some of the files.  I am
>  normally setting the repositories up for remote access via ssh.
>  
>  What is the right way to set up the repository, users/groups on the
>  repository or users/groups on the remote workstations as far as file
>  ownership and permissions go so that all users will be able to easily work
> on the files that each-other has submitted?  I've been through the FAQs and
> some of the documentation, and I've found some stuff on setting up remote
> ssh access to a repository, but nothing about how to setup file
>  permissions/ownership properly.
>  
>  Thanks,
>  
>  Les
>  
>  
>  
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 
> 
>