> > 5.1.1: I must have joined the list after this was discussed, but
> > it seems to me that creating symlinks is far more portable
> > (accross httpd servers) than creating Alias directives. Have
> > you talked about the possibility of prompting for the
> > document root, with /var/www as the default, for example?
>
> i was hoping that we could solicit some feedback from the non-admin
> httpd maintainers to get an idea of how many servers did and didn't
> support such a feature. i think the general consensus is that we
> should be agnostic of the documentroot and not mess around with files
> and symlinks in there if at all possible.
The current Debian Polciy says, section 11.5, says:
"Web Applications should try to avoid storing files in the Web
Document Root. Instead they should use the /usr/share/doc/package
directory for documents and register the Web Application via the
doc-base package. If access to the web document root is unavoidable
then use
/var/www
as the Document Root. This might be just a symbolic link to the
location where the system administrator has put the real document
root."
http://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-web-appl
This makes /var/www seem like the standard Debian default document
root (which can always be symlinked).
I find that it is much more web-server agnostic to create a symlink in
/var/www than to create an Alias in an apache config file.
> > 5.2: Should include HTTP_HOST environmental variable as well.
> > Perhaps we should recommend explicitely facilitating support
> > for multiple instances.
>
> added reference to that variable as well. now, what about multiple
> instances running out of the same virtualhost but different
> subdirectory?
Perhaps REQUEST_URI, SCRIPT_FILENAME, and SCRIPT_NAME.
> > PHP Policy Draft
> >
> > 4.1.1: Should NOT be of the form php-pear-PEARLIBRARYNAME.
>
> allright. so we have:
>
> ...
>
> does that sound right?
Sounds right to me. :-)
> > 4.1.2: "XXX: does this conflict with piotr's recommendation for
> > having pear work only in /usr/local?": yes, but I think that
> > he is wrong about that. ;-)
>
> having thought about it, there's probably some combination of cmdline
> params that could be used to have pear work out of the /usr/share
> repository when installing prepackaged pear modules, and have it
> otherwise default to working out of /usr/local/share/php otherwise.
That sounds very nice indeed.
Charles
--
Don't lose
Your head
To gain a minute
You need your head
Your brains are in it
Burma-Shave
http://burma-shave.org/jingles/1947/dont_lose
Attachment:
signature.asc
Description: Digital signature