A potential client has allowed me to look at their code before jumping in to replace their current developer. Hosted on Slicehost, he has not used Capistrano, but merely has a Ruby script that uses rsync to synchronize server and local files. The script includes a long list of excluded directories where content is uploaded or there is some other reason not to sync.

This is like Heroku, which uses Git to accomplish more or less the same thing. In both cases I am uncomfortable to not have Capistrano's ability to roll back instantly to the last deployed version of code, at least not easily. That has been very useful in cases where something went wrong with a deployment.

Anyone do the syncing thing rather than Capistrano? Do you do anything, maybe with Git, to be ready to roll back and sync the last known working version of the code?

Scott
-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to