[Gforge-devel] My Recent Changes

[Robert Nelson]

Answers below.

> -----Original Message-----
> From: gforge-devel-bounces at lists.gforge.org [mailto:gforge-devel-
> bounces at lists.gforge.org] On Behalf Of Christian BAYLE
> Sent: Thursday, March 08, 2007 1:05 PM
> To: gforge-devel at lists.gforge.org
> Subject: Re: [Gforge-devel] My Recent Changes
> 
> Hi Robert
> 
> Great, do you plan to merge this in trunk? would be nice for me.

I will be merging it into the trunk.  I wanted to finish my testing first.
Also I figured I'd wait a few days to let your big commit settle down. :-)

> I'd like to reorganize a the source tree to make gforge easier to
> install on an ISP Box
> I think for example that all includes should be moved in the www/include
> dir that is usually the default include, remove the need of symlink for
> plugins.
> Would you find this useful or not?
> 

The include files in common/include don't really matter however the symlink
of the plugins does cause problems.  Most ISPs are running some sort of
Apache module like suphp which runs the PHP scripts as the user rather than
Apache.  One of the security checks is to ensure that the scripts and/or the
file a symlink points to is under the document root for that site.  If the
www directory of the plugin were copied to www/plugins rather than
symlink'ed it would work much better.

Included and required files can be located anywhere. 

I committed the script I use for installing GForge, it's a modified version
of gforge-install.sh called gforge-restricted.sh.  I added a modified
version of INSTALL called INSTALL.restricted.  That should give you an idea
of what I'm doing.

Also I spent some time to figure out the minimum set of file and directory
permissions required.

Basically I have a separate user called gforge, but it could be anything.
In that user's home directory I have a gforge subdirectory with the
following structure.

	~/gforge/opt	=	/opt/gforge
	~/gforge/var	=	/var/gforge
	~/gforge/etc	=	/etc/gforge


> Christian
>