ZendServer installs PHP CLI as part of the installation, and, as is customary for PHP 4.3+, includes a PEAR installer. It’s a good idea to install PEAR before installing PHPUnit as per the recommendation here.
- Open Zend\ZendServer\bin\go-pear.bat and change the line:
%PHP_BIN% -d output_buffering=0 -d PEAR\go-pear.pharto (see PHAR Runtime Configuration):
%PHP_BIN% -d output_buffering=0 -d phar.require_hash=0 PEAR\go-pear.pharThis will stop the fatal error:
phar...does not have a signatureas by default PHP will not process a PHAR archive without a signature.
- Run go-pear.bat
For Windows 7, make sure you open the console as an administrator, or the installer won’t be able to create some folders in the default install locations. At the command prompt enter:
#cd \program files\zend\zendserver\binand you should get something like this (I selected the system-wide install and accepted the default locations):
via Installing PHPUnit for PHP 5.3 on ZendServer | katsande.com.
Kevin Schroeder writes; Zend Server 5.6 is out. I’m actually pretty stoked about this release. Here’s a few reasons why.
- Zend Server CE now contains the full Zend Server stack. Why do I find this exciting? Because the upgrade path from CE to the full version is stupid easy. That means you can try out all of the features in Zend Server and if you don’t want them, just let the license expire. I call it a gateway drug. Seriously. Get Studio or PDT and try the deployment feature. If you’re not using it you’ll ask yourself “why am I not doing this?”
- All of you Mac users can finally stop bitching and complaining about the lack of Mac support. We don’t (and probably won’t) support Mac for production (does anyone besides Apple actually use their server products in production?) but for dev work you now get the full stack on your Mac. This is not GA yet but will be later on. If you want a preview release you can go to http://forums.zend.com/viewtopic.php?f=8&t=26873 .
- Fault tolerance in the Job Queue through MySQL clustering. In clustered environments job queue information has moved from local storage to remote MySQL storage. So you can have a single MySQL server sitting there, a clustered setup or RDS or some other cloud-based DB, it doesn’t matter. If it can be accessed using the MySQL drivers then it can be used by the new Job Queue.
via ESchrade – Pure PHP Goodness.