--- xml/htdocs/proj/en/glep/glep-0011.html 2003/08/12 17:02:43 1.2 +++ xml/htdocs/proj/en/glep/glep-0011.html 2003/08/13 08:43:18 1.3 @@ -33,9 +33,9 @@ Title:Web Application Installation -Version:1.2 +Version:1.3 -Last-Modified:2003/08/12 23:14:00 +Last-Modified:2003/08/13 17:02:43 Author:Troy Dack <tad at gentoo.org> @@ -77,12 +77,12 @@
  • 3. Virtual Host Support
  • -
  • 5. Application Permissions
  • +
  • 4. Application Permissions
  • Backwards Compatibility
  • @@ -303,10 +303,10 @@

    To assist administration of multiple virtual hosts a "VHost Configuration Tool" needs to be developed and implemented. Initial discussion regarding the VHost Config tool and proposed usage can be found at http://article.gmane.org/gmane.linux.gentoo.devel/10874.

    -

    It's the job of the VHost Config toolset to make a local instance of the web +

    It's the job of the VHost Config toolset to make a local instance of the web application run under a specific web server.

    -

    The VHost Configuration Utility will need to be a seperate package, maintained by Gentoo. -Apache .ebuilds will require the VHost Config tool as a dependency (DEPEND).

    +

    The VHost Configuration Utility will need to be a seperate package, maintained by Gentoo.

    +

    Web Server .ebuilds will require the VHost Config tool as a dependency (DEPEND).

    Bug #26293 [4] will be used to track the initial progress of the VHost Configuration Tool.

    The vhost-config must do three main things:

    @@ -321,7 +321,7 @@ server. As the tool matures support for other web servers can be added.

    -

    4.1 Single Host Installation

    +

    3.3 Single Host Installation

    For single host installations the .ebuild will make the required configurations changes and symlinks using the VHost Config tool to ensure that the web application is available to be served from:

    @@ -332,7 +332,7 @@ directories from /usr/share/webapps/${PF}/ as is appropriate.

    -

    4.2 Virtual Host Installation

    +

    3.4 Virtual Host Installation

    For installations that support multiple virtual hosts the .ebuild will install the web application into the default location and then leave configuration to the user through the VHost Config tool.

    @@ -340,20 +340,20 @@ /usr/share/webapps/${PF}/ to /var/www/<FQDN>/ by the VHost Config tool.

    -

    4.3 Configuration Files

    -

    As stated above web application site default configuration files are to be +

    3.5 Configuration Files

    +

    As stated above web application site default configuration files are to be installed into:

     /etc/webapps/${PF}/
     

    The files in this directory are then copied (not symlinked!) by the VHost Config tool to the Document Root for each instance of the app that is installed.

    -

    This will require the VHost Config toolset to emulate Portage's CONFIG_PROTECT +

    This will require the VHost Config toolset to emulate Portage's CONFIG_PROTECT behaviour for the web applications.

    -

    5. Application Permissions

    +

    4. Application Permissions

    Installing web applications and giving the web server ownership of the files is a security risk. This can possibly lead to application configuration files being accessed by unwanted third parties.

    @@ -416,7 +416,7 @@