I think /usr/share/PACKAGE/www is rather long and clumsy. May I suggest a /web directory. http://lists.debian.org/debian-webapps/2005/06/msg00029.html
The Web application can then store files based on /web/HTTP_HOST. /usr/share/PACKAGE/www doesn't account for the possibility that more than one website will use the package. The data will tend to be site specific and hence using the environment variable HTTP_HOST is sensible. For example: /web/example.com http://example.com/ It encourages a strong link to the URL. Things like http://example.com/blog with a link to /usr/share/wordpress can't really be done because you would need to account for the REQUEST_URI. I feel comfortable enough to suggest that each web application should have it's own HTTP_HOST aka domain. So each Web app will require use of subdomains off one domain host. This allows Web applications the full freedom to use REQUEST_URI of which many are designed to do already. This keeps URLs consistent and makes URL editing easier. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
