[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PHP application packaging policy/best practice?

On Tue, Jan 11, 2005 at 11:04:55PM +0100, Kees Leune wrote:
> On Tue, 11 Jan 2005 21:20:03 +0100, Pierre Habouzit
> <pierre.habouzit@m4x.org> wrote:
> > IMHO, web apps should be installed in /usr/share/*appname*/
> Agree; it seems that most of the responses boil down to that. The next
> question then is; what do you do with the tree under
> /usr/share/appname? I need .php files (files which are accessible by
> the PHP interpreter), .plib files (my own extensions; php files meant
> to be included; not served by apache), and possibly datafiles which
> are peristent over sessions. Right now, I am leaning to using
> /usr/share/appname/php

I go with /usr/share/appname/www to signify that is the web-root of my
install.  Some (redhat-infected people, I guess) use appname/htdocs.

> /usr/share/appname/lib

That'd work, or if you're interested in making it a more useful library, you
could put it in /usr/share/php/<app-or-library-name>, where everyone can
easily use it (with the added bonus that then you don't have to f**k with
the include_path in all your apps or php.ini to make your library easily

> /var/lib/appname

That's where my datafiles go.  /var/lib/phpwiki being the primary offender.

- Matt

Attachment: signature.asc
Description: Digital signature

Reply to: