[gentoo-dev] Re: [gentoo-core] [GLEP] Web Application Installation

[Max Kalika]

> ...
> Due to a lack of standard install method configuration files are at
> risk of being overwritten during upgrade, potentially causing system
> administrators down tine as they have to reconfigure web applications
> after an upgrade.

(typo) down time.  Also how about say "after each upgrade."

> 2. Application Location
> -----------------------
> ...
> A suggested alternative installation location for web applications,
> outside of the Document:

outside Document Root?

>	* for files to be served to clients::
>
>		/usr/share/webapps/<application>/files/

I think this should just be /usr/share/webapps/<application>/

>	* for documentation files (not served to clients)::
>
>		/usr/share/doc/webapps/<application>/

Perhaps keep things consistant and put docs in /usr/share/doc/${PF}.  This
way the current dodoc() and dohtml() utility functions can continue to be
used without extra effort on behalf of the ebuild writers.

> 3. Application Configuration
> ----------------------------
> ...
>	* Apache configuration directives:
>
>	   - install a sample file in::
>
>			/usr/share/doc/webapps/<application>/conf/
>
>	   the ebuild should inform the user how to include this
>	   information in their Apache configuration.
>
>	   - alternatively the configuration directives could be placed in::
>
>			/etc/apache{1,2}/conf/webapps/<application>
>
>	   this directory and the files in it should be included by the
>	   main Apache configuration file.
>
> By installing application configuration files in /etc Portage
> CONFIG_PROTECT features can be used to ensure that configuration files
are 
> not overwritten.

The eclass currently puts them as /etc/webapps/<application>.conf.  This
way they are parallel to the application configuration files and are also
web-server independent, all while being protected by CONFIG_PROTECT.  The
ebuild informs the user to how to activate the installed app which, when
executed,
just creates a link into the already-configured apache directory.


Some other difficulty I came across while installing various webapps that
we may want to address (perhaps not in this GLEP, but definitely sometime
down the road) are:

 - Determining what modules mod_php has built into it.  Currently, I have
   a quick and dirty function in the webapp eclass called check_php() which
   looks for a particular USE flag in /var/db/pkg/dev-php/mod_php*/USE.
   This probably needs to be a bit cleaner.
 - Certain web applications need to have write access to the directory where
   they are installed (curse them!) :-)
 - Great care must be taken to properly prepare the configuration files.
   For example, Horde config files have paths defined relative to the config
   file itself so some sed magic was used to fix a lot of it.

Otherwise I am thrilled to see all this progress.  Thank you!
Standardization should always be applauded. :-)

--mk

--
gentoo-dev@g.o mailing list