There's no such thing as an `export` (really) from Git [1], it works this way to ensure that you always have a copy of the code on the server, and often can simply `fetch` new code from the repository. Soe people have used this as something like `intrusion detection` (recognising changes on the server, that aren't represented in the repository.)
The :export, and :remote_cache strategies differ slightly in that each time the `clone` is executed, of course - but in :remote_cache the clone is simply a `fetch` - so you're not copying the whole repository each time. [1] - http://stackoverflow.com/questions/160608/how-to-do-a-git-export-like-svn-export [2] - http://www.webdigi.co.uk/blog/2009/how-to-detect-if-your-webserver-is-hacked-and-get-alerted/( - the part about "hash each file", this is what happens in Git, of course.) - HTH, Lee -- * 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
