This is essentially how Github releases their application. http://github.com/blog/470-deployment-script-spring-cleaning
There is a Rails plugin that wraps up these ideas for easy integration: http://github.com/blog/470-deployment-script-spring-cleaning Caveat: I haven't personally tried either of these approaches in my applications. On Jan 8, 1:34 pm, myobie <[email protected]> wrote: > I have been contemplating that copying all my deployed code out of a > cached git repo and into a folder on the server for every deploy isn't > really necessary, since I already have it managed by git in a way that > I can checkout any version of the code. > > What I am thinking is that I create a new set of recipes that only > have a current directory and that it is just a checked out git repo. > Then, I can keep a RELEASES file up to date with the sha of the > release for rollback purposes. > > Has anyone tried this before? > > I hate to break new ground if there is something existing I can > contribute to.
-- * 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
