Glad I could make you smile :) I do use the same basic layout as the basic deployment strategies. What I've done so far is:
- Create a custom deployment strategy, based on remote_cache, but using 'svn switch' instead of 'svn update' (we deploy from tags), and I believe using 'svn export' to create the release copy. - Set hosts and other options via multistage (staging tags go in a different place than production tags) - Add completely custom one-off tasks like 'tail' (runs 'tail -f' on relevant logs). - Hooks all over the place: - Auto-generate the deploy tag before update_code - Fix permissions after update_code (svn doesn't seem to get it right) - Set database.yml after update_code (by parsing ~/.my.cnf) -- this allows those credentials to be auto-generated on instance creation - Send notification emails after symlink I mostly leave the default tasks in there because they make sense, but they feel like more of a skeleton from which to start my own hacking. Sometime this week, I intend to finally start using that patch I submitted for dynamic roles -- that will pull down role descriptions via REST, as the cluster configuration may change faster than we want to checkin deploy.rb (and it will eventually change atuomatically). On Sun, Jun 22, 2008 at 4:06 PM, Jamis Buck <[EMAIL PROTECTED]> wrote: > > On Jun 20, 2008, at 1:00 PM, David Masover wrote: > > > Even when deploying Rails, I often gut the default deploy tasks, and > > add dozen or so hooks. > > David, this totally made my day. I love to hear this kind of stuff. > The default deployment tasks are a starting point that work fine for > most folks, but they are certainly not intended to be a perfect > solution for everyone. It makes me smile to hear of people that are > unafraid to roll their own deployment recipes. > > To stay on-topic, the multistage stuff is more-or-less documented here: > > http://weblog.jamisbuck.org/2007/7/23/capistrano-multistage > > (It's the first hit if you google for "capistrano" and "multistage") > > - Jamis > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
