In a new post to her blog Lorna Mitchell has written a beginner's guide to deployment for web based applications in response to a recent email from a reader.

I [replied to the email] with some suggestions (and my consulting rate) attached, and we had a little email exchange about some improvements that could fit in with the existing setup, both of the hardware and of the team skills. Then I started to think ... he probably isn't the only person who is wondering if there's a better way. So here's my advice, now with pictures!

She's broken it up into a few different sections to make it a bit more easily digestible:

• A "starting point" where there's a development, staging and live environments
• Using source control to manage code
• Branching for effective coordination
• Integration of automated deployment

She also mentions other "bonus points" like making a build server, documentation generation and Javascript/CSS minification.

In a new post from Lukas Smith's blog he talks about the project's move to Subversion and away from CVS and how that's affected the language's development in a very positive way.

I remember that back when I was co-RM for PHP 5.3 one of the very painful parts was the crying and moaning about the commit freezes we put into place while packaging up a new release. The reason being we were on CVS, if people kept committing while a release was being tested it would effectively prevent any sort of QA.

Because of problems like this (and many others), the group decided to drop CVS for their development and head to the brighter land of Subversion. So, instead of having days when no commits are allowed, correct branching and testing make it much easier to develop one of the web's most popular languages.

The change came with some new branching techniques and some of the developers in the group aren't as happy about how they're handled. Some new tools have been developed to help minimize the risks that these methods could cause, though, including this site.

Felix Geisendorfer has a new post today showing off an example of his screencasting abilities. Specifically, the video looks at using vendor branching to keep your CakePHP installation up to date.

So here I go with my very first screencast to be published. The topic is how to use vendor branching with CakePHP which is one of many ways to keep your CakePHP version up to date.

The video is 15(ish) minutes long and covers, from start to finish, the process of grabbing the latest CakePHP build from the subversion repository and install it automatically to your system.

As a plus, Felix also includes links to the software he used to make the screencast for those that are curious.

Felix Geisendorfer has a new post today showing off an example of his screencasting abilities. Specifically, the video looks at using vendor branching to keep your CakePHP installation up to date.

So here I go with my very first screencast to be published. The topic is how to use vendor branching with CakePHP which is one of many ways to keep your CakePHP version up to date.

The video is 15(ish) minutes long and covers, from start to finish, the process of grabbing the latest CakePHP build from the subversion repository and install it automatically to your system.

As a plus, Felix also includes links to the software he used to make the screencast for those that are curious.