best practice approach re freezing rails & SVN/Capistrano approach ???


I’ve just had to
“freeze rails” for the first time as Dreamhost isn’t on the latest
version yet. So I’m assuming I will freeze rails into my application,
add the new vendor/rails directory to my subversion repository (
i.e. will commit all the rails files as part of my application), then
run “cap deploy” to upload the whole application including the local
rails files to my server.

Q1 - Is this the current best practice approach? If not what are most rails developers doing here re SVN and deployment approach?

Q2 - This approach seems to impact the deployment turn-around time (given the Capistrano / SVN approach), i.e. will take quite a while now to deploy each new version onto my hoster for testing. Am I missing something here perhaps?


Mike Clark recently blogged about managing Rails versions w/ Capistrano: