Sigh... never mind, I need to stop asking dumb questions right before going to lunch.
I simply put the common code in a plugin and added the following line to Capfile. Duh! load 'vendor/plugins/cap_extensions/lib/cap_extensions' Jon Garvin wrote: > I've got a bunch of customizations in our deploy.rb for one Rails > project and am finding that I'm copy/pasting a lot of that over to > another Rails project that I'm converting to use Cap2. Is there a > suggested method for sharing this kind of code between projects? Maybe > as an svn:external plugin? > > For instance, I've got the following in deploy.rb. If I make changes to > deploy:health_check, like adding additional commands, I'd prefer to just > add it once, and have it affect all of our projects, for all of our > developers. > > ------------------------------ > after 'deploy:cleanup', 'deploy:health_check' > namespace :deploy do > desc <<-DESC > Runs a series of commands on the server to give a snapshot of > it's overall health. It's up to you to actually read the output > and make a diagnosis. > DESC > task :health_check do > puts '################ Beginning Health Check #################' > run 'uptime' > run 'free -m' > run 'vmstat -s | egrep "(memory|cache|swap)"' > run 'vmstat 3 5' > end > end > > -- http://www.5valleys.com/ --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
