Possible simple solution for publicweb problem
| From: | Greg Beaver | Date: | Tue, 02 Sep 2003 03:29:55 +0000 |
| Subject: | Possible simple solution for publicweb problem | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-20984@lists.php.net to get a copy of this message | ||
Hi all,
To recap, I brought up the idea of having a publicweb role which would be for installed files that are like phpDocumentor's web server - they require installation into a subdirectory of document root.
This might be completely unnecessary - what if the existing data directory were a subdirectory of document root? This would only require a change to the installer, and documentation changes. No need for a new role.
The installer would simply add documentation that the data directory should be a subdirectory of a document root, if possible, and the web installer could suggest a location by autodetecting from whence it was run.
Is there any data that should never be exposed to web scrutiny that would make this a bad idea? If not, it would both solve the problem and work for existing packages without modification. Of course, existing installations would have to be moved, which might be a real problem.
Regards,
Greg