Re: Re: potential public web solution

I don't think that there is a solution for several virtual servers, and I don't even think that it would be useful. on one hand there is a package like HTML_TreeMenu that provides only datafiles, but on the other hands there could be something like (ok, it's not pear, but it jumped to my mind) phpmyadmin, where every instance needs it's own config-file. I'd keep it like Gentoo-Linux does, when i emerge phpmyadmin there it simply installs it to /home/httpd/htdocs/phpmyadmin. and every other web-package does it this way (gallery, cacti, cvsweb, and so on). What i'm doing is put the default-docroot into another dir and use /home/httpd/htdocs just as a container for web-packages, and these will be symlinked to all the virtual servers that need it (if it's just datafiles) or be copied (when it's something that can only be used for one instance). Let the admin (or the customer) take care about it! there _can't_ be an automated solution for it (how would you determine wether THIS virtual server needs the files or not?). Yes, this is a real pain if you have many many virtual servers, but how often will it be the case that you want to provide a certain pear-package by default to all you virtual servers? I really like Greg's way, it's clean and simple. Just my 2 euro-cents ;-) Stephan Greg Beaver wrote:

Hi Roman, It will not work - each virtual host should have a local PEAR installation that overrides the global one, but the same principle could be applied. Greg Roman Neuhauser wrote:

# greg@chiaraquartet.net / 2003-10-03 12:51:15 -0400:

Here's an idea for a simple solution to the publicweb problem.

$ pear config-set doc_root /usr/share/web/www $ pear config-set data_dir /usr/share/web/www/pear-files/pear

how well will that work on machines with multiple virtual hosts?