Re: write permission issues with repository hosting
From: David Weintraub <qazwart_at_gmail.com>
Date: Mon, 1 Nov 2010 09:36:13 -0400
On Oct 29, 2010, at 11:41 AM, "Polder, Matthew J" <matthew.j.polder_at_lmco.com> wrote:
The files don't have to be owned by the user. For example, the user might be a member of a group with read/write access. However, when a new revision is written, the new revision will be owned by the user running the server process.
Normally, you don't use the file:/// protocol except for private repositories. Otherwise, all users can directly manipulate the source repository itself. In fact, I never use file:/// even on my private repository. It's easy enough to run svnserve on my machine.
Have the svnserve and httpd processes owned by the same user and drop file:/// access. Then chown the files to that user and set permissions on all files to 664.
-- David Weintraub David_at_Weintraub.name Sent from my iPhone while riding in my Ferrari. (Jealous?)Received on 2010-11-01 14:37:14 CET
This is an archived mail posted to the Subversion Users mailing list.