I'm playing around with Capistrano 2.0. The first order of business
for me (after upgrading my recipe of course) is to move over the
custom implementation I wrote for our SCM system. I'm hitting an issue
with the deploy_via copy option. Our SCM system (Accurev) doesn't like
exporting or checkout out code while inside a working copy (workspace
in Accurev terms).

I checked out the code for the copy strategy. It would be trivial for
me to make my own deployment strategy that exports into a different
directory (/tmp for example). Is that the preferred approach or is
this something that Cap2 should support by default?

Doug Barth
Orbitz Worldwide


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to