1 |
>> >>> I'm not sure if you are overcomplicating this by trying to use Unix |
2 |
>> >>> permission. Have you instead considered webdav? You can restrict this |
3 |
>> >>> to particular (apache) users/groups, directories, files. It also uses |
4 |
>> >>> lockfiles so with two users editing a file simultaneously will cause a |
5 |
>> >>> warning when you try to save it. |
6 |
>> >> |
7 |
>> >> How does webdav relate to something like subversion? Do they |
8 |
>> >> compliment each other or are they substitutes? |
9 |
>> >> |
10 |
>> >> - Grant |
11 |
>> > |
12 |
>> > WebDAV has no version control. It is just an extension to HTTP for |
13 |
>> > distributed authoring. It supports locking files and methods which make |
14 |
>> > it more filesystem-like. AFAIK SVN uses WebDAV for its HTTP transfer |
15 |
>> > protocol. |
16 |
>> |
17 |
>> Got it. It sounds like I could use WebDAV in conjunction with |
18 |
>> subversion or git. I'll look into that. |
19 |
> |
20 |
> The reason I mentioned webdav(s) earlier was because you can have granular |
21 |
> control of what each user can access. You need specify only what |
22 |
> directory/file you want them to be able to access and they shouldn't have |
23 |
> access to anything else. |
24 |
|
25 |
I believe the same is accomplished through the use of subversion's |
26 |
path-based authorization. |
27 |
|
28 |
> Also, you don't need to give them shell access - which I find |
29 |
> (psychologically) more reassuring. ;-) |
30 |
|
31 |
I like that a lot. The way I understand it, in order to edit a file |
32 |
with subversion, you would check out the file from the repository to |
33 |
your local machine, edit it on your local machine, and commit your |
34 |
changes to the repository. How does the workflow change with webdav? |
35 |
|
36 |
- Grant |