Hi Kenneth, A lot of what you appear to have done [2] has been done in the forthcoming 2.5.6 release that I'm testing at the moment, if you want to compare notes, I'll merge it into the next release provided it all works.
Also regarding your daemon kit stuff, there is a 'new' (ok, I'm using require, and some new paths) to load the `old` tasks back in under 2.5.6, so by default it ships with no assumptions about environments (unix + releases/ + current/ with rollbacks) -- this is maybe an ideal place for you to place your daemon-kit files. *Infact, anyone that wants to try the new version, and help me work out the kinks, I'll push it to github this evening, and we can maybe run a few test deploys on people's low-impact projects? I don't have many things I can deploy for testing purposes without a big risk to my clients.* Thanks for the time kenneth, also - you can follow capistrano development on twitter at @capistranorb. - Lee 2009/5/26 Kenneth Kalmer <kenneth.kal...@gmail.com> > Hi everyone > > Just thought this might be interesting to some of you. I spent the evening > baking capistrano [1] support into DaemonKit [2]. I cleaned up the standard > deploy recipe to make it daemon friendly and remove a lot of Rails cruft, > and by default the generated capistrano configs uses the multistage features > of the capistrano-ext gem. > > Kind regards > > [1] http://www.opensourcery.co.za/2009/05/26/capistrano-for-your-daemons/ > [2] http://github.com/kennethkalmer/daemon-kit > > -- > Kenneth Kalmer > kenneth.kal...@gmail.com > http://opensourcery.co.za > @kennethkalmer > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to capistrano-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
