Re: PHP application packaging policy/best practice?

[Jérôme Warnier <jwarnier@beeznest.net>]

Le vendredi 07 janvier 2005 à 14:19 +0100, Kees Leune a écrit :
> Hi,
> 
> I am preparing an ITP for a PHP application that is currently under
> development at my place of employment. While thinking about packaging
> it, I was wondering if there is any PHP application policy or best
> practice. I am now leaning to a setup as follows:
> 
> /usr/lib/appname/php      Publicly loadable PHP pages
> /usr/lib/appname/lib        Included PHP libraries (not reachable via httpd)
> /var/lib/appname             Persistant data
> /etc/appname/appname.cfg Configuration
> /etc/appname/apache.conf   Apache configuration (symlink from
> /etc/apache/conf.d)
> 
> Note that I chose /usr/lib over /usr/share because according to the
> FHS, /usr/share is meant for "all read-only architecture independent
> data files". Although PHP files are read-only and architecture
> indepedent, I consider them as programs.
> 
> Any thoughts?
I collected some interesting Debian packaging Web Applications policy
drafts some time ago:
http://glasnost.beeznest.org/articles/184

I accept any comments, especially improvements of course.

> -Kees