Hi Jamis, I was curious if you'd be interested in a patch that would expose an option (e.g. :use_geminstaller) that would add as remote dependencies each of the gems found in a geminstaller.yml file (Chad Wooley's GemInstaller gem). Basically, if the option were set, deploy:check would also read the geminstaller.yml file and parse the dependencies. Furthermore, an additional task (e.g. :install_gems) could be exposed to actually install each of the gems.
Until now, one of the steps I've put into my deploy:update is a method that runs Chad's geminstaller executable. However, this can slow down deployment considerably, and might work nicely if I moved it out of the standard deploy process. On this note, is there a way to currently require that deploy:check is successful before actually invoking a recipe? This would eliminate the need for the developer to mindfully run deploy:check before trying to re-deploy (in the event that perhaps the geminstaller.yml file has changed). Lastly, do you feel this would be more appropriate to just hack directly into deploy:check, or should I push this into the RemoteDependency class? btw, I see potential problems when deploying to multiple servers (i.e. a db server, a web server, a load balancer, etc) in that you'd probably want to require a distinct set of gems per role. However, I imagine these issues could be worked out by exposing more configuration options (either in geminstaller or capistrano). -John --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
