The branch is only used internally to ensure a clean working directory, from which to copy the release files. It's not another "branch" that you have to maintain, and it's never pushed back to the source control. Also with git, having a new branch costs 1 inode and about 3b of disk space… so it shouldn't matter.
Having reviewed the article very briefly, I can say that his point revolves around not maintaining different branches, and you won't have to. The Capistrano branches, as I said exist only to ensure a clean copy of the code is available on the disk to be copied into the release directory. A bigger topic is the release directories themselves, they can really build up, but there's a task to clean them up. - Lee On 3 August 2011 14:17, Zeedy <[email protected]> wrote: > I'm trying to follow the strategy outlined by Eric Sink in his book on > distributed source control: > http://www.ericsink.com/vcbe/html/web_development.html > > Basically, a web application need only ever deploy from the same > release branch, i.e. we don't need to create a new branch for every > deployment. > > > On Aug 2, 5:01 pm, Lee Hambley <[email protected]> wrote: > > What problem are you trying to solve by not checking out the branch? Cap > > does this to ensure some measure of cleanliness, and make sure that your > > deploys are always atomic. > > -- > * 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
