Skip to content
Browse files

Suggest Mongrel and Capistrano in the default bundle

  • Loading branch information...
1 parent 39ebd6e commit 834a45d8a2ae225b775c51d8ae266a4550e9fba1 @dhh dhh committed Feb 9, 2010
Showing with 17 additions and 11 deletions.
  1. +17 −11 railties/lib/generators/rails/app/templates/Gemfile
View
28 railties/lib/generators/rails/app/templates/Gemfile
@@ -1,28 +1,34 @@
source 'http://gemcutter.org'
<%- if options.dev? -%>
-gem "rails", :path => "<%= Rails::Generators::RAILS_DEV_PATH %>"
+gem 'rails', :path => '<%= Rails::Generators::RAILS_DEV_PATH %>'
<%- elsif options.edge? -%>
-gem "rails", :git => "git://github.com/rails/rails.git"
+gem 'rails', :git => 'git://github.com/rails/rails.git'
<%- else -%>
-gem "rails", "<%= Rails::VERSION::STRING %>"
+gem 'rails', '<%= Rails::VERSION::STRING %>'
# Bundle edge Rails instead:
-# gem "rails", :git => "git://github.com/rails/rails.git"
+# gem 'rails', :git => 'git://github.com/rails/rails.git'
<%- end -%>
<% unless options[:skip_activerecord] -%>
-gem "<%= gem_for_database %>"<% if require_for_database %>, :require => "<%= require_for_database %>"<% end %>
+gem '<%= gem_for_database %>'<% if require_for_database %>, :require => '<%= require_for_database %>'<% end %>
<% end -%>
+# Use mongrel as the web server
+# gem 'mongrel'
+
+# Deploy with Capistrano
+# gem 'capistrano'
+
# Bundle the extra gems:
-# gem "bj"
-# gem "hpricot", "0.6"
-# gem "sqlite3-ruby", :require => "sqlite3"
-# gem "aws-s3", :require => "aws/s3"
+# gem 'bj'
+# gem 'hpricot', '0.6'
+# gem 'sqlite3-ruby', :require => 'sqlite3'
+# gem 'aws-s3', :require => 'aws/s3'
# Bundle gems for certain environments:
-# gem "rspec", :group => :test
+# gem 'rspec', :group => :test
# group :test do
-# gem "webrat"
+# gem 'webrat'
# end

4 comments on commit 834a45d

@KieranP

capistrano isn't a gem needed to run applications though, so you might wrap it in a 'group :development'

@dmathieu

Is that a really good idea ?
Anyone who doesn't know rails very well will install capistrano and mongrel by default when they don't need it. And they won't be using them as they won't explicitly know they exist.

@yfeldblum

That's only if "anyone who doesn't know rails very well" uncomments every suggestion in the Gemfile without thinking about it or researching it first.

I agree that the capistrano gem dependency might do well to be assigned to the :development group (or alternatively to a :deployment group, since you need it for deployment rather than for development).

@Aupajo
Aupajo commented on 834a45d Feb 11, 2010

+1 yfeldblum

Please sign in to comment.
Something went wrong with that request. Please try again.