Because a deploy is rarely only what's under version control. Think about generated config files, generated assets, bundler invocations.
The timestamp feature is so that you can rollback a bad deploy in its totality (with the caveat of DDL changes to databases) Github has a recipe for converting to a git-pull single release directory if that suits you, search their blog. On Jan 5, 2012, at 6:13 PM, tim <[email protected]> wrote: > Hey guys. > > Just out of curiosity... > > I was wondering why capistrano keeps past checkouts instead of using > the version control mechanism itself. > > In other words why not a "git reset --hard revno" or something > similar? > > Cheers. > > -- > * 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 -- * 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
