Bad idea to add users to the apache group?

[Namor]

We're running into an issue in my office with this. One of our guys has some PHP scripts that need to write to a text file. So that file needs to be in the apache group (or world writeable, which we obviously do not want). But we also need another user to be able to access and write to the file via her account. It seems the easiest way to do this would be to make apache own the file and add the usrs to the apache group.

Is this a bad idea?

Thanks for you opinions.

[rizzo]

I thing by default apache will write files with apache:users ownership, so the file would already be owned by the users group. Just make the file group writeable and you should be OK.

[rac]

If it doesn't, I would recommend going the other way around: putting the apache user in a group (new, if necessary), and adding both apache and the other user to this group. You can make the enclosing directory owned by the group and setgid, in order to force files created under it to be owned by said group, if that helps.
_________________
For every higher wall, there is a taller ladder