Nicholas, Bear in mind that changing something like this for us as maintainers, will break a lot of people's deploys; until the advent and proliferation of bundler, we've been effectively prevented from making changes to the `deploy.rb` file from the Gem, because people see this behavior as part of the Gem, and not what it is, which is a part of their project.
To that end, the web/app role being blurry is a hangover from the days of mongrel and the script/spinner boot mechanics of early Rails (< 2.0) projects. With the proliferation of bundler, and renewed interest in the project, changes such as these will be forthcoming, along with additional roles for :assets for those people using the Rails 3.1 asset pipeline (this is already built in as of 2.8.0, a couple of apparent bugs not withstanding) I can recommend only that you take the deploy.rb out of the Gem, and put into your project, customize the roles as you see fit. This is what I did to enable easier `rails-less` deploys, and I made a Gem out of it. I'm not sure this really satisfies your question, and if you feel strongly I'd appreciate a "bug" report via Github, I think it's fairly reasonable to consider, in a world where the destination between app and web is well established, that we draw a clearer line between the responsibilities. - Lee -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
