Jordi, Your process is pretty much bang-on… the only recommendation I would make is to make sure there's no craziness in the live environment with selinux or anything like that which might cause problems or introduce vulnerabilities.
There's a little work to do to make sure images persist between releases, essentially you'll modify the `:shared_children` variable, add 'images/uploads' (or whatever you like) - which will be created when you do `cap deploy:cold`. From there, you have to add a custom task which symlinks that directory to `public/images/uploads` (or, wherever) after each deploy; that stuff is pretty trivial though. Regarding paths/etc - I would recommend you don't mess with the existing application; incase you have problems, run the new-redeployable-git-versioned-app on the same server, another apache host, private port, and a whole other working directory; that way you aren't risking the production environment or extended downtime. I figure during that process, you get the redeploy optimized, and the `go-live` step is simply an apache vhost changeover? - Anything I missed? -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
