Holy moley, has it been almost a year since I blogged about a potential CakePHP deployment task. Since a few people have hit me up in Twitter and in the comments for that blog post, I thought I would share my progress on this task. To be blunt, I decided it was a waste of time to do it.
Why? Well, there plenty of options out there to help you with application deployment already. I talked about many of them in the talk I gave at PHPQuebec back in March. In the end, there is no reason to NOT use an existing tool to handle this other than you cannot (or in some cases will not) use one of these tools. I picked Capistrano because:
Sure, being able to type 'cake deploy' would be nice for those people who are using Cake and have things setup completely according to the default configuration, but one little change and the whole thing might just blow up. Capistrano and Phing are the two tools I would recommend to any PHP devs trying to work out automated deployment.
Given the number of permutations that can be part of an install, I am not confident that 'cake deploy' would be up to the task. When I think about all the stuff I have to deploy that is not just PHP code at work, I can't imagine making it all work in a CakePHP task. That's not to say that someone smarter than me can't figure it out.