Jamis Buck wrote: > My vision for Capistrano 2.0 is to follow the suggestions a few > people have offered and decouple "Capistrano-the-part-that-executes- > remote-processes" from "Capistrano-does-rails-deployment". The "core" > capistrano bit would be installable standalone, with no defaults. The > rails-specific bits would then depend on capistrano-core.
Jamis, let me know if you see it this way at all: 1. Tools that help you write shell scripts in ruby (eg run, sudo). Call it MetaShell. 2. Multiple SSH. 3. Rails deployment scripts. I see #1 and #2 standing on their own. I see #3 depending on #1, but only depending on #2 if you want to run it remotely. #3 itself breaks up into SCM Web/App servers System level tasks Rails specific tasks --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
