Re: potential public web solution

Hi, 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? Greg Roman Neuhauser wrote:

# greg@chiaraquartet.net / 2003-10-03 13:13:55 -0400:

Roman Neuhauser wrote:

that's quite an administrative nightmare, isn't it? I have a web server with ~50 sites, do you want me have 50 parallel PEAR installations?

As it stands right now, none of them can use packages like HTML_TreeMenu through PEAR, they have to simply unzip the thing directly.

but your proposal doesn't make the situation any better for me.

The point would be that each user can independently use the pear installer on their local site, and maintain that installation themselves, the way they maintain the source code they upload themselves.

there's one user: me (ok, and two or three colleagues)

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.