Re: potential public web solution

# greg@chiaraquartet.net / 2003-10-03 13:23:51 -0400: > Roman Neuhauser wrote: > ># greg@chiaraquartet.net / 2003-10-03 13:13:55 -0400: > >>I assume you don't support all 50 site's web pages, but I > >>don't maintain a 50 site web server, so I could be wrong :) > > > > that's exactly what we do. we create, and maintain, sites and > > applications for people who are not capable of, or unwilling to, > > do it for themselves. we don't even provide shell access to our > > customers. > > OK, well, my idea would allow the retrieval of a relative path. You can > use Apache aliasing to make sure that the relative path works for every > virtual domain. In other words, the full path to the data files would > not matter in a web context, only the relative path from document_root "/" > > http://foo.example.com/pear-files/pear/HTML_TreeMenu/images > http://foo2.example.com/pear-files/pear/HTML_TreeMenu/images > > These would be aliases for each other. > > Would this solve the problem in your case? This is almost exactly what I was thinking of for some time now. Just declare /pear/<package> as the official standard access point to web fodder, and you're set. Or, if you want to get really fancy, you could massage httpd.conf during install. IOW: prefix/lib/php <-- classess prefix/share/php <-- web media or something along those lines... -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html