Using Capistrano gives me a few advantages that just using svn for deployment doesn’t

* pushes to multiple servers from one location
* ability to rollback deployments if there is a problem
* ability to perform other tasks automatically as part of a deployment

You can do all those by hand, sure. But I prefer to let capistrano do it for me

I am glad that you blogged about how you use capistrano to deploy cakephp applications, and I was very interested to know how you do it!
You mentioned it as a comment over at Felix’s blog post entitled “Deploying with Git” at debuggable.com.

Thanks for this blog post.

The thing I liked about Cap was it’s lack of XML, it was really easy to read and write the config.

I would like to see a full deploy script however. One that checks out the source, runs unit tests and then ftps the diff to the server. I have heard that this is possible with both Cap and Phing but I haven’t gone through the trials of setting it up (yet).

Thanks for the basic tutorial though

thank for the guide. I’m still looking for the ultimate setup myself – i’ll try to write something more about cap

I had to set the Ruby path a bit like here
http://cakephp.org/screencasts/view/6 you guys explained for the Cake Console command line

then moving to the app/ directory:
————————————————–
C:\yourappDir> cap -f config/deploy.rb deploy
————————————————–
and…WOW!

Dan

Your deploy.rm file gave me an error, some “:” not really understood by Capistrano.

I modified it as follows:
set :application, “nameofyourapp”
set :repository, “svn://location.ofrepo.com”

# If you aren’t deploying to /u/apps/#{application} on the target
# servers (which is the default), you can specify the actual location
# via the :deploy_to variable:
set :deploy_to, “/website/#{application}”
set :checkout, “export”
# If you aren’t using Subversion to manage your source code, specify
# your SCM below:
# set :scm, :subversion

role :web, “www.yoursite.com”

desc “This will deploy the app”
task :deploy do
run “svn –quiet –force #{checkout} #{repository} #{deploy_to}”
end