Hi I am just glad someone is willing to step in so quickly. I think capistrano and webistrano is both great products but with an original focus on ruby/rails applications. I believe that with a bit of effort ( a bit more in webistrano) it could easily be made to be more generic. Currently I have to "bend" webistrano a bit to get it working nicely with our internal deployment methodologies.
I have been working hard to get our specific tomcat/jboss deployments working well in a loadbalanced 24/7 environment doing simultaneous and sequential deployments and I am excited about how capistrano has enabled me to do this and about the future of the tool. I am hopefull that when I get a chance I can make the tasks I have written a bit more generic so anyone can use it for tomcat deployments. There is'nt really that much deployment tools for tomcat so I reckon that if you could design a good generic deployment strategy for tomcat together with some generic "load balancer" interfaces to lb's like modjk and mod_proxy (even F5) you could have a whole new slew of users. Especially with closer integration with webistrano to simplify the usage. The single sign on in webistrano is sure to score lots of points in corporate environments. Regards On Feb 26, 11:55 am, Lee Hambley <[email protected]> wrote: > Hi All, > > I'm a little suspect of the Webistrano/Macistrano guys taking over > development, as I feel particularly that Webistrano limits the capabilities > of capistrano and limits it usefulness for non-rails projects. > Whilst there's still a market for simple-one-push rails deploys, with > accountability; But I would be hoping for some kind of reassurance that > Web/Macistrano would remain separate projects, and would not affect > capistrano in any way. > > I do feel that someone that knows the Capistrano internals should take over, > I'd have volunteered, except my skills lay in using Capistrano, for complex > deploys; not particularly in changing internals, and fixing bugs, and those > sorts of things. > > Whoever takes it over should be prepared to start living in IRC, and start > up a drive to get documentation written... and try and drive it as *the* way > to handle deployment. > > Even since Net::SSH-Multi - my interest in capistrano has slipped a little, > as for the most part, my deploys aren't very compatible with the capistrano > notion of a single app over a few roles of servers. > > I'm looking forward to whatever happens with Capistrano, Jamis has left us > with an exceptional bit of code, we owe it to him to make the right decision > about where to take it next. > > I will be forking copies of the libraries on Github, to make some changes to > the way cap logs out to the screen, some things that have come up from time > to time on the mailing list, about problems with how, and where capistrano > logs, as well as some stuff I want to do with the output to the screen (does > that count as logging?) > > Before we all fork-off and make our own changes, I fear that there will be > no go-to-guy for a 'right' version of capistrano that scares me a lot, as it > raises the barrier to entry far higher than it needs to be... > (will_paginate... Vs. mislavs_will_paginate anyone?) > > - Lee > > 2009/2/26 Simone Carletti <[email protected]> > > > Thanks for your feedback Karel! > > > I agree that Capistrano needs more documentation and I'm happy to hear > > someone else is available to contribute. > > I must confess I didn't notice your message before, I'm going to post a > > reply athttp://groups.google.com/group/capistrano/msg/654e5e84d45f9098 > > > Talking about the future of maintainership, I'm going to contact Jonathan > > directly to accelerate the process. > > > It would be wonderful to get a feedback from Jamis about this topic. > > I'm a bit concerned about how we can carry on development without the need > > to force people to change gem name or repository. > > > -- Simone > > > On Thu, Feb 26, 2009 at 11:36 AM, Karel Minarik > > <[email protected]>wrote: > > >> Karel --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
