Hi Lee, I agree that there should be an app-stack aware Capistrano where you define your stack and get much better defaults.
I totally agree with the goal of making deploying non-rails (and non-spin) applications easier but I think it should be done more unobtrusive than now and it shouldn't break existing deployments for a 2.x release. The 'deploy' recipe is probably used by everyone (update_code, symlink, ...) - where deployments differ is the actual method of starting/stopping/restarting the app. This should be the 'extension' that I load and we should ship nice defaults for passenger, mongrel, php&co. E.g. in Webistrano there is a project type that gives you those tasks by default. I think we should have a discussion about what should be there by default, what should be in the extensions, what to do with generators, and so on. So there are many open questions that we should think of before pressing a release. I would recommend releasing only the patches/fixes that we gathered during the lasts weeks and do a real 'point'-release. The app-stack stuff and patches that Mathias and I have for parallelization and code-cleanup are more something for a 2.6 or event 3.0 release that should go under a lot of discussions and code reviews. Cheers, Jonathan --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
