[kdewebdev-site] Permissions continued

Eric Laffoon eric at kdewebdev.org
Fri Mar 4 14:39:42 EST 2005


On Friday 04 March 2005 11:32 am, Andras Mantia wrote:
> On Friday 04 March 2005 21:17, Eric Laffoon wrote:
> > On Friday 04 March 2005 10:17 am, Andras Mantia wrote:
> >
> > Problems arise...
> > in /public_html/
> > Could not change permissions for
> > fish://kdewebdev@kdewebdev.org/home/kdewebdev/public_html/docs/common
> >/xml.dcl. It seems you did not verify this was group writable. These
> > types of errors have made it more challenging to fix.
>
> It is:
> -rw-rw-r--    1 amantia  kdewebde     6801 Mar  3 03:03 xml.dcl

Strange. I have a couple files in kallery that are in the project and block me 
when I try to upload too, as well as the scripts and another directory in 
public_html that Quanta can't seem to identify correctly as directories, but 
as files which expand like directories. Maybe I should send you the project 
file, but it's also on site.
>
> so it's group writable...
> But remember, that this mail referred to the /var/lib/cvs, the list with
> problem directories under /home/kdewebdev is in the other mail I sent
> today to the list.

Now I'm really confused. I've looked at the CVS and it seems like all 
directories are group writable. All files are read only and this seems to 
work fine. You are still having trouble pulling CVS? I had weird problems 
before and did a fresh checkout and everything seemed okay so I could not 
complain. Have you tried that?
>
> > Some directories like developer/public_html/ I only made the
> > public_html/ directory g+w -R. I didn't see a need to add content
> > below server root. Is this creating a real problem for you? If so I
> > can change it.
>
> It's enough if public_html is group writable. Just make sure you don't
> forget the g+s, otherwise if someone created a subdirectory it won't
> belong to the kdewebdev group. This is a problem both in /var/lib/cvs
> and in /home.
>
> > I've checked through the rest of the site. Primarily this was not an
> > issue if I was uploading but regardless I think I have about all of
> > it corrected, except for /public_html/css which I'm very reluctant to
> > make group writable. Changes can be submitted to CVS but a new site
> > developer could blindly change CSS and upload it and break every page
> > on the site. Because of the grief we went through arriving at a
> > visual layout that works I'm not inclined to open any change
> > capability here that hasn't been fully reviewed.
>
> I don't mind if some areas are not group writable, just we need to know
> what and where can we commit and where can we upload. And where we (any
> of us) can commit and upload should have the correct permissions, so we
> don't stay in someone other's way.

This brings up a question about project files. For instance you have release 
files in the project that I don't need to upload. I guess I mark them as 
uploaded. Then if you update and commit won't Quanta want to upload again? 
What if I mark the file as don't upload? Will that cause problems for you?

Maybe we need even more thought for Team functionality for 3.5? ;-)
>
> Andras

-- 
Eric Laffoon
Project Lead - kdewebdev module


More information about the kdewebdev-site mailing list