I actually did something like this recently. It was fairly trivial to setup, but I'd be willing to contribute it to the framework if anyone is interested. I sent this to a client to test and it was very helpful in evaluating system requirements: http://bradley-holt.blogspot.com/2008/09/im-currently-working-on-project-where.html
On Mon, Oct 13, 2008 at 8:23 PM, lupusBE <[EMAIL PROTECTED]> wrote: > > Maybe creating a php file that scans info like the one you get with > phpinfo() > and tells you what is needed to get things working would be handy for some > people. > > You can then easily send a list (the one you get on the screen) to your > providers support channel > > Could also be handy if you have made a project for a customer and you are > not sure the hosting of the customer has everything that is needed for the > project to run. > You could then run this on the customers hosting or let the customer > himself > run it. > You could use this also before upgrading a your library directory. > if current version is 1.6 and you want to update to 1.7 but 1.7 has other > requirements you could make the script scan if the hosting has the needed > requirements. > > Drupal for example also does a check like this. > > http://framework.zend.com/issues/browse/ZF-4592 > -- > View this message in context: > http://www.nabble.com/script-that-you-can-prerun-on-your-hosting-to-see-if-all-needed-extensions-are-available-tp19965228p19965228.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > -- Bradley Holt [EMAIL PROTECTED]
