On Mon, Oct 3, 2011 at 6:01 PM, Grant <emailgr...@gmail.com> wrote: >>> >>> I'm not sure if you are overcomplicating this by trying to use Unix >>> >>> permission. Have you instead considered webdav? You can restrict this >>> >>> to particular (apache) users/groups, directories, files. It also uses >>> >>> lockfiles so with two users editing a file simultaneously will cause a >>> >>> warning when you try to save it. >>> >> >>> >> How does webdav relate to something like subversion? Do they >>> >> compliment each other or are they substitutes? >>> >> >>> >> - Grant >>> > >>> > WebDAV has no version control. It is just an extension to HTTP for >>> > distributed authoring. It supports locking files and methods which make >>> > it more filesystem-like. AFAIK SVN uses WebDAV for its HTTP transfer >>> > protocol. >>> >>> Got it. It sounds like I could use WebDAV in conjunction with >>> subversion or git. I'll look into that. >> >> The reason I mentioned webdav(s) earlier was because you can have granular >> control of what each user can access. You need specify only what >> directory/file you want them to be able to access and they shouldn't have >> access to anything else. > > I believe the same is accomplished through the use of subversion's > path-based authorization. > >> Also, you don't need to give them shell access - which I find >> (psychologically) more reassuring. ;-) > > I like that a lot. The way I understand it, in order to edit a file > with subversion, you would check out the file from the repository to > your local machine, edit it on your local machine, and commit your > changes to the repository. How does the workflow change with webdav?
It doesn't need to. From the user's perspective, the URI to the repo changes. That's pretty much it. (I.e. we went from svn://servername/path to https://servername/svn/path ) -- :wq
