On Oct 19, 2007, at 4:44 PM, Mislav Marohnić wrote:
On 10/20/07, Jamis Buck <[EMAIL PROTECTED]> wrote: Because it is easy. Feel free to change your deployment strategy accordingly.I know I can change it, I just wondered why not svn export by default. I fail to see how export is less "easy" than checkout.Phillip, currently you can't update the working copy. "cap deploy:update_code" will create a new release (not svn update), and if you try to manually svn update one of the working copies the update will probably fail because Capistrano messes up the working copy by deleting dirs/setting up symlinks.
Well, that's not entirely true. You _can_ update the working copy, you just have to do it on a specific file or directory. Which is great when you're working on a newish product and you keep tweaking things like CSS and JS and views, and you don't want to do a full- fledged deploy. You can also tweak directly on the server and commit from there--not a recommended best-practice, to be sure, but it has come in handy before, especially when you're first trying to get a new app deployed and running.
I suppose that's the primary reason cap uses checkout and not export by default, because we do that kind of tweaking/updating pretty often at 37signals, especially on products that are new.
- Jamis
smime.p7s
Description: S/MIME cryptographic signature
