Hi capistrano users, I want to give the Cap 2 Preview a test drive however I already have a working capistrano 1 configuration in place for a project that I wanted to leave in place for the other developers to use as is until I work out the kinks with capistrano 2 for our project and ensure that moving to Cap 2 will be mostly painless.
So my question is, is it possible to keep the config/deploy.rb as is while slowly trying to convert the Capfile to be more capistrano 2 compliant? I'm thinking I can 1. Run capify <my project dir> 2. take the contents of config/deploy.rb and copy into Capfile 3. Delete the load statements generated by the capify command 4. Find out which tasks blow up (most likely all the deploy based ones) and fix those. A quick glance seems to indicate that this will work but I figure it might be worth asking before spending hours learning that via some 'magic' the config/deploy.rb will get loaded and there is no way to prevent it. Are there better ways than what I'm thinking? On another note. I had a little request. Would it be possible to add some stub documentation to the capify command, please? When I try asking capify for --help it says there is no such thing as help :-) $ capify --help --help does not exist Cheers, Alain --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
