News Feed
Sections




News Archive
feed this:

Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Community News:
Packagist Latest Releases for 09.14.2014
September 14, 2014 @ 08:09:50

Recent releases from the Packagist:
0 comments voice your opinion now!



Community News:
Packagist Latest Releases for 09.13.2014
September 13, 2014 @ 08:09:25

Recent releases from the Packagist:
0 comments voice your opinion now!



SitePoint PHP Blog:
18 Critical Oversights in Web Development
September 12, 2014 @ 13:09:23

The SitePoint PHP blog has a new post today sharing what they (well the author, George Fekete) see as the top 18 critical oversights common to web development in recent years. While the examples are in PHP, the principles could apply across multiple other languages.

Over the past years I had the opportunity to work on some interesting projects, complex in nature with an ongoing development, constantly upgrading, refactoring and adding new features to them. This article will cover the biggest coding oversights most PHP developers make, when dealing with medium and large projects. Oversights such as not differentiating between development environments or not implementing caching and backup. [...] The root of these problems lies mainly in developers' knowledge and experience, especially the lack of it.

He's broken them up into three different overall types: design, application and database levels. Included in his list are things like:

  • Developing with error reporting off
  • Not implementing caching
  • Not using automated tests
  • Not differentiating between read / write queries
  • Not using transactions
  • No backup
  • No monitoring

Check out the full post for the rest of the items on the list, all including examples and explanations.

0 comments voice your opinion now!
critical oversights development list top18

Link: http://www.sitepoint.com/18-critical-oversights-web-development/

That Podcast:
Episode 7 The one where we didn't even bother with a topic
September 12, 2014 @ 10:48:08

"That Podcast", hosted by PHP community members Beau Simensen and Dave Marshall has released their latest episode, Episode #7: The one where we didn't even bother with a topic.

That's right, Beau and Dave are back! After what turned out to be a whole month since their last episode, the spend some time catching up on a bunch of things that have gone on in that time. Most importantly, Dave explains why dogs need passports. Who knew? Plus some other techy things. They keep it a little shorter than usual (only an hour and a half, yo!) on account of Dave not feeling so well. Also, Dave quits That Podcast because nobody has ever used his awesome voicemail app. Oh wait, no, that is a lie. He didn't quit. The other part was true about nobody leaving a voicemail, though. It makes them both sad.

You can listen to this latest episode either through the in-page player or by downloading the mp3 directly. If you enjoy the episode, consider subscribing to their feed to get this and other great episodes as they're released.

0 comments voice your opinion now!
thatpodcast ep7 podcast topic davemarshall beausimensen

Link: http://thatpodcast.io/episodes/episode-7-the-one-where-we-didn-t-even-bother-with-a-topic/

Community News:
Laravel Framework Introduces Liferaft
September 12, 2014 @ 09:25:04

The development group behind the Laravel framework have introduced a new tool that aims to make it easier to report bugs with the framework (not the applications built with them): Laravel Liferaft.

To encourage active collaboration, Laravel currently only accepts pull requests, not bug reports. "Bug reports" may be sent in the form of a pull request containing a failing unit test. [...] A failing unit test or sandbox application provides the development team "proof" that the bug exists, and, after the development team addresses the bug, serves as a reliable indicator that the bug remains fixed.

Following along with this method, Liferaft provides a simple way to download a clean copy of the framework, make the needed changes for the pull request and automatically submit it via GitHub back to the project for handling. In this video on Laracasts Taylor Otwell walks you through a simple example of using it to submit an issue back (and what happens behind the scenes).

0 comments voice your opinion now!
liferaft laravel framework bugfix unittest pullrequest

Link: https://laracasts.com/lessons/introducing-laravel-liferaft

Community News:
Packagist Latest Releases for 09.12.2014
September 12, 2014 @ 08:03:22

Recent releases from the Packagist:
0 comments voice your opinion now!




Matthew Weier O'Phinney:
Deployment with Zend Server (Part 6 of 8) - Page Caching
September 11, 2014 @ 14:57:08

Matthew Weier O'Phinney has posted his sixth part (of eight) in his "deployment with Zend Server" tips and tricks. In this latest post he talks about page caching.

This is the sixth in a series of eight posts detailing tips on deploying to Zend Server. The previous post in the series detailed setting job script status codes. Today, I'm sharing some tips around setting up page caching, and jobs for clearing the Zend Server page cache.

He starts off describing what Zend Server offers in the way of page caching and provides an example (with screenshots) of how he sets his up to work with multiple subdomains. He then shows how to set what variable the caching looks at to tell the difference between pages and how to clear the cache on deploy. He includes a simple script to help with that, running through a list of paths and calling the flush on each.

0 comments voice your opinion now!
zendserver deployment tips series part6 page caching

Link: https://mwop.net/blog/2014-09-11-zend-server-deployment-part-6.html

Inviqa techPortal:
My top ten favourite PhpSpec limitations
September 11, 2014 @ 11:15:31

On the Inviqua techPortal today Marcello Duarte lists out his top ten favorite limitations with the PhpSpec testing tool. PhpSpec is a tool where the tests are driven by specifications, focusing on the "how".

PhpSpec is enjoying a growth in popularity lately, probably related to the recent release of 2.0. Lots of people have been playing with it and trying to get to grips with what it can do. Naturally they try to do the same things they would with other testing tools. Soon they find out they can't. "Oh! This PhpSpec has some many limitations I can't do this I can't do that". Ironically, other people make positive comments about the same "limitations". So I decided to publish a list of my top ten favourite limitations of PhpSpec, and why I love them so much.

His limitations list includes things like:

  • I can't test private methods
  • You can't have code coverage
  • I can't use a data provider
  • My tests can't follow a code standard

Check out the full article for more of his list and some code examples ot help clarify each topic.

0 comments voice your opinion now!
phpspec testing behavior specification limitations top10 list

Link: http://techportal.inviqa.com/2014/09/11/my-top-ten-favourite-phpspec-limitations/

Nate Turner:
Spinning Up Symfony 2 Development Environments With Vagrant
September 11, 2014 @ 10:57:13

Nate Turner has posted a tutorial to his site sharing a step-by-step method for creating Symfony2 development environments with Vagrant. Vagrant (and Puppet) allow you to create a scriptable setup process that creates a VM with the same settings every time, making it easier to destroy and recreate as needed.

When we use Vagrant to create new virtual development environments we avoid the very real possibility that we could mess up our personal development machines. People have used virtual machines for development for years. [...] Managing installed applications across a teams VMs is a pain. Why not just include a Vagrantfile and a few Puppet manifests instead? Instead of passing around a virtual machine a few gigabytes in size, just include your Vagrant and Puppet in a project's source control. That's it. In future tutorials we will be using the environment we create here to start a new virtual machine running Symfony 2 with the above command.

He walks you through each of the steps, complete with commands and configuration changes to make everything cooperate:

  • Create a Symfony Project with Composer
  • Setting up Vagrant
  • Provisioning with Puppet / Symfony's Requirements
  • Set up a new VirtualHost
  • Set Apache to run as the Vagrant user

He's also posted the complete working script over on his GitHub account.

0 comments voice your opinion now!
development environment symfony2 vagrant puppet tutorial

Link: http://nater1067.github.io/blog/2014/08/25/spinning-up-symfony-2-development-environments-with-vagrant/


Community Events





Don't see your event here?
Let us know!


interview deployment release podcast threedevsandamaybe developer zendserver development laravel code framework tips introduction community application list conference language series api

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework