On Nov 29, 2006, at 6:02 PM, [EMAIL PROTECTED] wrote: > The 'self' referred is the current actor in the specific task. I want > to provide an actor instance > for the existing machine rather than build a mock actor instance that > will eventually and constantly > break in the future.
That would be brilliant, but I don't think it's setup that way. In my perusal of the code there was only one Actor class and everything is built around execute_on_servers and establish_connection. It might be possible to subclass Actor and override these to do what you're talking about. For an existing example, the railsmachine gem just uses system. (railsmachine/recipes/svn.rb) Geoffrey Grosenbach --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
