Archive for January 31st, 2008
PHP Developer - January 31st, 2008
In a new article on DevShed, the spotlight is on putting Apache “in jail” with chroot, but they also include a section on setting up PHP to work inside it.
In this conclusion to a six-part series on Apache configuration and installation, you will learn how to use chroot to put Apache in jail, how to prepare PHP to work in jail, and more.
The article is an excerpt from the O’Reilly book “Apache Security” and shows how to get PHP to cooperate by installing it normally and then setting up some shared libraries to be used in the jail. They note one common problem - an issue with PHP accessing sendmail - that can be solved easily with a change to php.ini for the setup.
Continue Reading ·
PHP Developer - January 31st, 2008
This new post from Jon Lebensold (on the KillerPHP blog) introduces you to a handy feature of the Zend Framework - View Helpers.
In summary, View Helpers are great for encapsulating forms, grids and other functionality that could eventually be bound to a different data source or even be pushed back to the user through a simple AJAX call.
Example code on how to use them is included showing a sample helper that adds Ajax functionality to a form’s submit and pushes the response values back out into a div on the page.
Continue Reading ·
PHP Developer - January 31st, 2008
Mike Willbanks has posted an introduction he’s written up giving some helpful hints at tuning your servers and PHP applications for performance.
The focus of this post is not to show performance related items to specific PHP frameworks since many bottlenecks actually apply before running the framework itself that should certainly be solved up front. Therefore in this posting I attempt to look at simple items that can be deployed in order to produce finer tuned systems.
He talks about a few different aspects:
- PHP Performance Tuning (opcode caching, apc file priming, includes, loops, etc)
- RDBMS Performance Tuning (indexes in queries, query caching, archiving)
- HTTP Performance Tuning (content compression, css sprites, limit modules, etc)
Continue Reading ·
PHP Developer - January 31st, 2008
According to Tony Bibbs, PHP’s real problem is itself.:
So what do I mean when I say PHP’s problem is PHP itself? […] One word. Sustainability.
He suggests that, while PHP has made a big splash in the areas it’s hit, it is still tripping over its own feet. PHP, the language, can meet the needs of just about any sort of web development that might come down the line, but when good PHP developers are so hard to find, why should any organization bother with working it into their technology stack?
Comments on the article responds to the “chicken and egg situation” Tony has presented and how things like user groups can help stoke the fires of PHP’s presence in not only the budding web developers but also in the professionals looking to expand their horizons.
Continue Reading ·
PHP Developer - January 31st, 2008
Lukas Smith has posted some ominous thoughts about the future of the LAMP stack in the online development world - specifically asking if the popularity of the grouping could be what might ultimately cause its downfall.
The issue is that there is simply not enough top qualified talent that knows LAMP well enough to hire. Or maybe its just too hard to find them? It seems all the good guys are already hired. As a result companies end up looking for other technology, not because they actually believe that these technologies are any better or worth the license fees that these usually require to be paid up…
He suggests two things that could be possible lead-ins to the “demise” of LAMP - the fact that LAMP just isn’t taught along side other languages in school and that, since PHP is only just now getting into the offices of the “major players”, there hasn’t been enough time to prove to them that PHP has worth in their business.
Be sure to check out some of the great comments on this one.
Continue Reading ·