Deploying Sites : Capistrano


#1

I have three distinct configurations I need to maintain:

  • local dev
  • staging server (for client approval and test)
  • production server

Right now I’m relying on rsync and sweat to get things right.

Obviously Capistrano looks like the silver bullet, but it seems to rely
on Subversion over http as a dependency. Is this correct?

I’m running svn on my local machine and backing it up nightly. I know,
bad, bad. Is there a workaround for using Cap on a file:/// repository?

Thx


#2

Steve,

You might want to check out the “deploy by copy” recipe that Jim
Morris posted last month:

http://lists.rubyonrails.org/pipermail/rails/2006-February/
020821.html

  • Jamis