I'm relatively new to rails and capistrano -- and new to web development in general. I've been using a capistrano recipe to deploy my code -- using git as scm -- from my dev box to the production server without fully understanding the reasoning or strategy behind the process.
The recipe makes the production server a bare git repo. Each deployment version is kept; the active one is referenced via symlink to current directory. I copied this deployment solution, for lack of anything better, and have been happy with it. Now as I prepare and consider deployment for a second project, I'm trying to understand what it does and why. This solution seems a bit heavyweight to me. Why would we make our production server a bare -- authoritative -- repository? Why wouldn't we just push the working code out to the server with scp or rsync and leave it out of the scm loop? TIA -- * 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
