CakePHP Application Deployment: RFC post

May 16th, 2008

A co-worker of mine always complains that people don't read the RFC that covers a topic related to making their own stuff work with our stuff. He's old sk00l like that. Although my co-worker is a tad out-of-touch with the realities of programming these days (as in the amount of people who actually read the RFC when they can simply use someone else's library / module / function / application is very small), I thought I would at least adhere to some semblance of standards and do a blog posting about my plans for making CakePHP application deployment easier.

While I really prefer to use tools like this for deployment, I understand that not everyone wants to mess with standalone programs and configuration files. I've been asked before about Cake-specific deployment techniques, so I figure the easiest way is to see about adding a task to the Cake console. Let's call this 'cake deploy'.

As I explained on the mailing list I am looking for opinions on what sort of things should be part of the 'cake deploy' task. Right now, my thoughts are as follows:

  • cake deploy config
  • - setup and edit configuration parameters. Initially I thought of setting things like transport method (ssh, ftp), logins and passwords, remote location, source directory, and destination directory. The configuration file would be stored locally in APP/config
  • cake deploy - seems pretty self-explanatory to me.

In the RFC thread on the CakePHP mailing list, someone mentioned they'd like to see rsync, but I'm trying to avoid having to external programs required to make the deployment work. Or, at least, use as few as possible. Anyhow, if you have any thoughts on this feel free to add them to the comments.