RubyGems - railties - Versions diffs - 3.1.0.rc1 → 3.1.0.rc2 - Mend

railties 3.1.0.rc1 → 3.1.0.rc2

Files changed (57) hide show

data/CHANGELOG +2 -0
data/guides/assets/images/radar.png +0 -0
data/guides/assets/images/vijaydev.jpg +0 -0
data/guides/rails_guides/helpers.rb +1 -1
data/guides/source/action_view_overview.textile +6 -103
data/guides/source/active_record_basics.textile +2 -2
data/guides/source/active_record_querying.textile +32 -4
data/guides/source/active_record_validations_callbacks.textile +5 -3
data/guides/source/active_support_core_extensions.textile +4 -4
data/guides/source/api_documentation_guidelines.textile +2 -2
data/guides/source/caching_with_rails.textile +5 -5
data/guides/source/command_line.textile +78 -71
data/guides/source/configuring.textile +90 -74
data/guides/source/contribute.textile +2 -2
data/guides/source/contributing_to_ruby_on_rails.textile +3 -3
data/guides/source/credits.html.erb +16 -8
data/guides/source/generators.textile +3 -3
data/guides/source/getting_started.textile +1 -1
data/guides/source/i18n.textile +1 -1
data/guides/source/initialization.textile +311 -310
data/guides/source/migrations.textile +4 -4
data/guides/source/rails_on_rack.textile +6 -6
data/guides/source/routing.textile +1 -1
data/guides/source/testing.textile +2 -2
data/lib/rails/application.rb +17 -12
data/lib/rails/commands.rb +1 -1
data/lib/rails/commands/benchmarker.rb +3 -3
data/lib/rails/commands/console.rb +2 -1
data/lib/rails/commands/profiler.rb +3 -3
data/lib/rails/commands/server.rb +2 -1
data/lib/rails/configuration.rb +6 -0
data/lib/rails/engine.rb +1 -1
data/lib/rails/generators.rb +8 -2
data/lib/rails/generators/css/assets/assets_generator.rb +13 -0
data/lib/rails/generators/{rails/assets/templates/stylesheet.css.scss → css/assets/templates/stylesheet.css} +1 -2
data/lib/rails/generators/css/scaffold/scaffold_generator.rb +16 -0
data/lib/rails/generators/rails/app/app_generator.rb +1 -1
data/lib/rails/generators/rails/app/templates/Gemfile +2 -2
data/lib/rails/generators/rails/app/templates/config/application.rb +0 -11
data/lib/rails/generators/rails/app/templates/config/environments/development.rb.tt +3 -0
data/lib/rails/generators/rails/app/templates/config/environments/production.rb.tt +4 -2
data/lib/rails/generators/rails/app/templates/config/initializers/wrap_parameters.rb.tt +2 -2
data/lib/rails/generators/rails/app/templates/test/performance/browsing_test.rb +1 -1
data/lib/rails/generators/rails/assets/USAGE +1 -1
data/lib/rails/generators/rails/assets/assets_generator.rb +2 -9
data/lib/rails/generators/rails/plugin/templates/Rakefile.tt +3 -3
data/lib/rails/generators/rails/plugin_new/templates/Rakefile +8 -3
data/lib/rails/generators/rails/scaffold/scaffold_generator.rb +2 -11
data/lib/rails/generators/test_unit/performance/templates/performance_test.rb +1 -1
data/lib/rails/railtie.rb +7 -7
data/lib/rails/railtie/configurable.rb +2 -0
data/lib/rails/tasks/assets.rake +12 -1
data/lib/rails/tasks/documentation.rake +8 -2
data/lib/rails/tasks/misc.rake +1 -1
data/lib/rails/version.rb +1 -1
metadata +56 -9
data/lib/rails/generators/rails/scaffold/templates/scaffold.css.scss +0 -58

data/CHANGELOG CHANGED

@@ -1,5 +1,7 @@
 *Rails 3.1.0 (unreleased)*
+* The new rake task assets:clean removes precompiled assets. [fxn]
 * Application and plugin generation run bundle install unless --skip-gemfile or --skip-bundle. [fxn]
 * Fixed database tasks for jdbc* adapters #jruby

data/guides/assets/images/radar.png ADDED

Binary file

data/guides/assets/images/vijaydev.jpg ADDED

Binary file

data/guides/rails_guides/helpers.rb CHANGED

@@ -15,7 +15,7 @@ module RailsGuides
     def author(name, nick, image = 'credits_pic_blank.gif', &block)
       image = "images/#{image}"
-      result = content_tag(:img, nil, :src => image, :class => 'left pic', :alt => name)
+      result = content_tag(:img, nil, :src => image, :class => 'left pic', :alt => name, :width => 91, :height => 91)
       result << content_tag(:h3, name)
       result << content_tag(:p, capture(&block))
       content_tag(:div, result, :class => 'clearfix', :id => nick)

data/guides/source/action_view_overview.textile CHANGED

@@ -929,7 +929,7 @@ Creates a scope around a specific model object like form_for, but doesn‘t crea
 h5. file_field
-Returns an file upload input tag tailored for accessing a specified attribute.
+Returns a file upload input tag tailored for accessing a specified attribute.
 <ruby>
 file_field(:user, :avatar)
@@ -1037,7 +1037,7 @@ Sample usage (selecting the associated Author for an instance of Post, +@post+):
 collection_select(:post, :author_id, Author.all, :id, :name_with_initial, {:prompt => true})
 </ruby>
-If @post.author_id is already 1, this would return:
+If <tt>@post.author_id</tt> is 1, this would return:
 <html>
 <select name="post[author_id]">
@@ -1080,8 +1080,6 @@ Sample usage:
 option_groups_from_collection_for_select(@continents, :countries, :name, :id, :name, 3)
 </ruby>
-TODO check above textile output looks right
 Possible output:
 <html>
@@ -1132,13 +1130,13 @@ h5. select
 Create a select tag and a series of contained option tags for the provided object and method.
-Example with @post.person_id => 1:
+Example:
 <ruby>
 select("post", "person_id", Person.all.collect {|p| [ p.name, p.id ] }, { :include_blank => true })
 </ruby>
-could become:
+If <tt>@post.person_id</tt> is 1, this would become:
 <html>
 <select name="post[person_id]">
@@ -1189,7 +1187,7 @@ h5. file_field_tag
 Creates a file upload field.
-If you are using file uploads then you will also need to set the multipart option for the form tag:
+Prior to Rails 3.1, if you are using file uploads, then you will need to set the multipart option for the form tag. Rails 3.1+ does this automatically.
 <ruby>
 <%= form_tag { :action => "post" }, { :multipart => true } do %>
@@ -1400,102 +1398,6 @@ number_with_precision(111.2345)     # => 111.235
 number_with_precision(111.2345, 2)  # => 111.23
 </ruby>
-h5. evaluate_remote_response
-Returns +eval(request.responseText)+ which is the JavaScript function that form_remote_tag can call in +:complete+ to evaluate a multiple update return document using +update_element_function+ calls.
-h5. form_remote_tag
-Returns a form tag that will submit using XMLHttpRequest in the background instead of the regular reloading POST arrangement. Even though it‘s using JavaScript to serialize the form elements, the form submission will work just like a regular submission as viewed by the receiving side.
-For example, this:
-<ruby>
-form_remote_tag :html => { :action => url_for(:controller => "some", :action => "place") }
-</ruby>
-would generate the following:
-<html>
-<form action="/some/place" method="post" onsubmit="new Ajax.Request('',
-  {asynchronous:true, evalScripts:true, parameters:Form.serialize(this)}); return false;">
-</html>
-h5. link_to_remote
-Returns a link to a remote action that's called in the background using XMLHttpRequest. You can generate a link that uses AJAX in the general case, while degrading gracefully to plain link behavior in the absence of JavaScript. For example:
-<ruby>
-link_to_remote "Delete this post",
-  { :update => "posts", :url => { :action => "destroy", :id => post.id } },
-  :href => url_for(:action => "destroy", :id => post.id)
-</ruby>
-h5. observe_field
-Observes the field specified and calls a callback when its contents have changed.
-<ruby>
-observe_field("my_field", :function => "alert('Field changed')")
-</ruby>
-h5. observe_form
-Observes the form specified and calls a callback when its contents have changed. The options for observe_form are the same as the options for observe_field.
-<ruby>
-observe_field("my_form", :function => "alert('Form changed')")
-</ruby>
-h5. periodically_call_remote
-Periodically calls the specified url as often as specified. Usually used to update a specified div with the results of the remote call. The following example will call update every 20 seconds and update the news_block div:
-<ruby>
-periodically_call_remote(:url => 'update', :frequency => '20', :update => 'news_block')
-# => PeriodicalExecuter(function() {new Ajax.Updater('news_block', 'update', {asynchronous:true, evalScripts:true})}, 20)
-</ruby>
-h5. remote_form_for
-Creates a form that will submit using XMLHttpRequest in the background instead of the regular reloading POST arrangement and a scope around a specific resource that is used as a base for questioning about values for the fields.
-<ruby>
-<%= remote_form_for(@post) do |f| %>
-  ...
-<% end %>
-</ruby>
-h5. remote_function
-Returns the JavaScript needed for a remote function. Takes the same arguments as +link_to_remote+.
-<ruby>
-<select id="options" onchange="<%= remote_function(:update => "options", :url => { :action => :update_options }) %>">
-  <option value="0">Hello</option>
-  <option value="1">World</option>
-</select>
-# => <select id="options" onchange="new Ajax.Updater('options', '/testing/update_options', {asynchronous:true, evalScripts:true})">
-</ruby>
-h5. submit_to_remote
-Returns a button input tag that will submit form using XMLHttpRequest in the background instead of a regular POST request that reloads the page.
-For example, the following:
-<ruby>
-submit_to_remote 'create_btn', 'Create', :url => { :action => 'create' }
-</ruby>
-would generate:
-<html>
-<input name="create_btn" onclick="new Ajax.Request('/testing/create',
-  {asynchronous:true, evalScripts:true, parameters:Form.serialize(this.form)});
-  return false;" type="button" value="Create" />
-</html>
 h3. Localized Views
 Action View has the ability render different templates depending on the current locale.
@@ -1520,6 +1422,7 @@ You can read more about the Rails Internationalization (I18n) API "here":i18n.ht
 h3. Changelog
+* May 29, 2011: Removed references to remote_* helpers - Vijay Dev
 * April 16, 2011: Added 'Using Action View with Rails', 'Templates' and 'Partials' sections. "Sebastian Martinez":http://wyeworks.com
 * September 3, 2009: Continuing work by Trevor Turk, leveraging the Action Pack docs and "What's new in Edge Rails":http://ryandaigle.com/articles/2007/8/3/what-s-new-in-edge-rails-partials-get-layouts
 * April 5, 2009: Starting work by Trevor Turk, leveraging Mike Gunderloy's docs

data/guides/source/active_record_basics.textile CHANGED

@@ -64,8 +64,8 @@ There are also some optional column names that will create additional features t
 * *created_on* - Automatically gets set to the current date when the record is first created.
 * *updated_at* - Automatically gets set to the current date and time whenever the record is updated.
 * *updated_on* - Automatically gets set to the current date whenever the record is updated.
-* *lock_version* - Adds "optimistic locking":http://api.rubyonrails.com/classes/ActiveRecord/Locking.html to a model.
-* *type* - Specifies that the model uses "Single Table Inheritance":http://api.rubyonrails.com/classes/ActiveRecord/Base.html
+* *lock_version* - Adds "optimistic locking":http://api.rubyonrails.org/classes/ActiveRecord/Locking.html to a model.
+* *type* - Specifies that the model uses "Single Table Inheritance":http://api.rubyonrails.org/classes/ActiveRecord/Base.html
 * *(table_name)_count* - Used to cache the number of belonging objects on associations. For example, a +comments_count+ column in a +Post+ class that has many instances of +Comment+ will cache the number of existent comments for each post.
 NOTE: While these column names are optional they are in fact reserved by Active Record. Steer clear of reserved keywords unless you want the extra functionality. For example, "type" is a reserved keyword used to designate a table using Single Table Inheritance. If you are not using STI, try an analogous keyword like "context", that may still accurately describe the data you are modeling.

data/guides/source/active_record_querying.textile CHANGED

@@ -483,16 +483,16 @@ SQL uses the +HAVING+ clause to specify conditions on the +GROUP BY+ fields. You
 For example:
 <ruby>
-Order.group("date(created_at)").having("created_at > ?", 1.month.ago)
+Order.group("date(created_at)").having("created_at < ?", 1.month.ago)
 </ruby>
 The SQL that would be executed would be something like this:
 <sql>
-SELECT * FROM orders GROUP BY date(created_at) HAVING created_at > '2009-01-15'
+SELECT * FROM orders GROUP BY date(created_at) HAVING created_at < '2011-04-27'
 </sql>
-This will return single order objects for each day, but only for the last month.
+This will return single order objects for each day, but only those that are at least one month old.
 h3. Overriding Conditions
@@ -675,7 +675,7 @@ class Post < ActiveRecord::Base
   has_many :tags
 end
-class Comments < ActiveRecord::Base
+class Comment < ActiveRecord::Base
   belongs_to :post
   has_one :guest
 end
@@ -683,6 +683,10 @@ end
 class Guest < ActiveRecord::Base
   belongs_to :comment
 end
+class Tag < ActiveRecord::Base
+  belongs_to :post
+end
 </ruby>
 Now all of the following will produce the expected join queries using +INNER JOIN+:
@@ -700,6 +704,8 @@ SELECT categories.* FROM categories
   INNER JOIN posts ON posts.category_id = categories.id
 </sql>
+Or, in English: "return a Category object for all categories with posts". Note that you will see duplicate categories if more than one post has the same category. If you want unique categories, you can use Category.joins(:post).select("distinct(categories.id)").
 h5. Joining Multiple Associations
 <ruby>
@@ -714,18 +720,40 @@ SELECT posts.* FROM posts
   INNER JOIN comments ON comments.post_id = posts.id
 </sql>
+Or, in English: "return all posts that have a category and at least one comment". Note again that posts with multiple comments will show up multiple times.
 h5. Joining Nested Associations (Single Level)
 <ruby>
 Post.joins(:comments => :guest)
 </ruby>
+This produces:
+<sql>
+SELECT posts.* FROM posts
+  INNER JOIN comments ON comments.post_id = posts.id
+  INNER JOIN guests ON guests.comment_id = comments.id
+</sql>
+Or, in English: "return all posts that have a comment made by a guest."
 h5. Joining Nested Associations (Multiple Level)
 <ruby>
 Category.joins(:posts => [{:comments => :guest}, :tags])
 </ruby>
+This produces:
+<sql>
+SELECT categories.* FROM categories
+  INNER JOIN posts ON posts.category_id = categories.id
+  INNER JOIN comments ON comments.post_id = posts.id
+  INNER JOIN guests ON guests.comment_id = comments.id
+  INNER JOIN tags ON tags.post_id = posts.id
+</sql>
 h4. Specifying Conditions on the Joined Tables
 You can specify conditions on the joined tables using the regular "Array":#array-conditions and "String":#pure-string-conditions conditions. "Hash conditions":#hash-conditions provides a special syntax for specifying conditions for the joined tables:

data/guides/source/active_record_validations_callbacks.textile CHANGED

@@ -82,6 +82,7 @@ The following methods skip validations, and will save the object to the database
 * +increment!+
 * +increment_counter+
 * +toggle!+
+* +touch+
 * +update_all+
 * +update_attribute+
 * +update_column+
@@ -428,7 +429,7 @@ end
 The +validates_with+ helper takes a class, or a list of classes to use for validation. There is no default error message for +validates_with+. You must manually add errors to the record's errors collection in the validator class.
-To implement the validate method, you must have an +record+ parameter defined, which is the record to be validated.
+To implement the validate method, you must have a +record+ parameter defined, which is the record to be validated.
 Like all other validations, +validates_with+ takes the +:if+, +:unless+ and +:on+ options. If you pass any other options, it will send those options to the validator class as +options+:
@@ -914,20 +915,20 @@ h4. Creating an Object
 * +before_validation+
 * +after_validation+
 * +before_save+
-* +after_save+
 * +before_create+
 * +around_create+
 * +after_create+
+* +after_save+
 h4. Updating an Object
 * +before_validation+
 * +after_validation+
 * +before_save+
-* +after_save+
 * +before_update+
 * +around_update+
 * +after_update+
+* +after_save+
 h4. Destroying an Object
@@ -1010,6 +1011,7 @@ Just as with validations, it's also possible to skip callbacks. These methods sh
 * +increment+
 * +increment_counter+
 * +toggle+
+* +touch+
 * +update_column+
 * +update_all+
 * +update_counters+

data/guides/source/active_support_core_extensions.textile CHANGED

@@ -882,7 +882,7 @@ The macro accepts several methods:
 delegate :name, :age, :address, :twitter, :to => :profile
 </ruby>
-When interpolated into a string, the +:to+ option should become an expression that evaluates to the object the method is delegated to. Typically a string or symbol. Such a expression is evaluated in the context of the receiver:
+When interpolated into a string, the +:to+ option should become an expression that evaluates to the object the method is delegated to. Typically a string or symbol. Such an expression is evaluated in the context of the receiver:
 <ruby>
 # delegates to the Rails constant
@@ -3038,7 +3038,7 @@ Date.new(2010, 1, 31).change(:month => 2)
 h5(#date-durations). Durations
-Durations can be added and substracted to dates:
+Durations can be added to and subtracted from dates:
 <ruby>
 d = Date.current
@@ -3246,7 +3246,7 @@ DateTime.current.change(:month => 2, :day => 30)
 h5(#datetime-durations). Durations
-Durations can be added and substracted to datetimes:
+Durations can be added to and subtracted from datetimes:
 <ruby>
 now = DateTime.current
@@ -3367,7 +3367,7 @@ If the time to be constructed lies beyond the range supported by +Time+ in the r
 h5(#time-durations). Durations
-Durations can be added and substracted to time objects:
+Durations can be added to and subtracted from time objects:
 <ruby>
 now = Time.current

data/guides/source/api_documentation_guidelines.textile CHANGED

@@ -37,8 +37,8 @@ h3. Example Code
 Choose meaningful examples that depict and cover the basics as well as interesting points or gotchas.
-Use two spaces to indent chunks of code.—that is two spaces with respect to the left margin; the examples
-themselves should use "Rails code conventions":http://rails.lighthouseapp.com/projects/8994/source-style.
+Use two spaces to indent chunks of code--that is two spaces with respect to the left margin; the examples
+themselves should use "Rails coding conventions":contributing_to_ruby_on_rails.html#follow-the-coding-conventions.
 Short docs do not need an explicit "Examples" label to introduce snippets, they just follow paragraphs:

data/guides/source/caching_with_rails.textile CHANGED

@@ -112,7 +112,7 @@ As an example, if you wanted to show all the orders placed on your website in re
 <ruby>
 <% Order.find_recent.each do |o| %>
-  <%= o.buyer.name %> bought <% o.product.name %>
+  <%= o.buyer.name %> bought <%= o.product.name %>
 <% end %>
 <% cache do %>
@@ -162,17 +162,17 @@ class ProductSweeper < ActionController::Caching::Sweeper
   # If our sweeper detects that a Product was created call this
   def after_create(product)
-          expire_cache_for(product)
+    expire_cache_for(product)
   end
   # If our sweeper detects that a Product was updated call this
   def after_update(product)
-          expire_cache_for(product)
+    expire_cache_for(product)
   end
   # If our sweeper detects that a Product was deleted call this
   def after_destroy(product)
-          expire_cache_for(product)
+    expire_cache_for(product)
   end
   private
@@ -345,7 +345,7 @@ ActionController::Base.cache_store = MyCacheStore.new
 h4. Cache Keys
-The keys used in a cache can be any object that responds to either +:cache_key+ or to +:to_param+. You can implement the +:cache_key+ method on your classes if you need to generate custom keys. ActiveRecord will generate keys based on the class name and record id.
+The keys used in a cache can be any object that responds to either +:cache_key+ or to +:to_param+. You can implement the +:cache_key+ method on your classes if you need to generate custom keys. Active Record will generate keys based on the class name and record id.
 You can use Hashes and Arrays of values as cache keys.

data/guides/source/command_line.textile CHANGED

@@ -55,7 +55,7 @@ INFO: This output will seem very familiar when we get to the +generate+ command.
 h4. +rails server+
-Let's try it! The +rails server+ command launches a small web server named WEBrick which comes bundled with Ruby. You'll use this any time you want to view your work through a web browser.
+The +rails server+ command launches a small web server named WEBrick which comes bundled with Ruby. You'll use this any time you want to view your work through a web browser.
 INFO: WEBrick isn't your only option for serving Rails. We'll get to that in a later section.
@@ -65,7 +65,7 @@ Without any prodding of any kind, +rails server+ will run our new shiny Rails ap
 $ cd commandsapp
 $ rails server
 => Booting WEBrick
-=> Rails 3.0.0 application starting in development on http://0.0.0.0:3000
+=> Rails 3.1.0 application starting in development on http://0.0.0.0:3000
 => Call with -d to detach
 => Ctrl-C to shutdown server
 [2010-04-18 03:20:33] INFO  WEBrick 1.3.1
@@ -75,6 +75,8 @@ $ rails server
 With just three commands we whipped up a Rails server listening on port 3000. Go to your browser and open "http://localhost:3000":http://localhost:3000, you will see a basic Rails app running.
+You can also use the alias "s" to start the server: <tt>rails s</tt>.
 h4. +rails generate+
 The +rails generate+ command uses templates to create a whole lot of things. You can always find out what's available by running +rails generate+ by itself. Let's do that:
@@ -237,7 +239,7 @@ dependency  model
     create    test/unit/high_score_test.rb
     create    test/fixtures/high_scores.yml
     exists    db/migrate
-    create    db/migrate/20081217071914_create_high_scores.rb
+    create    db/migrate/20100209025147_create_high_scores.rb
 </shell>
 The generator checks that there exist the directories for models, controllers, helpers, layouts, functional and unit tests, stylesheets, creates the views, controller, model and database migration for HighScore (creating the +high_scores+ table and fields), takes care of the route for the *resource*, and new tests for everything.
@@ -267,11 +269,13 @@ h4. +rails console+
 The +console+ command lets you interact with your Rails application from the command line. On the underside, +rails console+ uses IRB, so if you've ever used it, you'll be right at home. This is useful for testing out quick ideas with code and changing data server-side without touching the website.
+You can also use the alias "c" to invoke the console: <tt>rails c</tt>.
 If you wish to test out some code without changing any data, you can do that by invoking +rails console --sandbox+.
 <shell>
 $ rails console --sandbox
-Loading development environment in sandbox (Rails 3.0.0)
+Loading development environment in sandbox (Rails 3.1.0)
 Any modifications you make will be rolled back on exit
 irb(main):001:0>
 </shell>
@@ -280,6 +284,8 @@ h4. +rails dbconsole+
 +rails dbconsole+ figures out which database you're using and drops you into whichever command line interface you would use with it (and figures out the command line parameters to give to it, too!). It supports MySQL, PostgreSQL, SQLite and SQLite3.
+You can also use the alias "db" to invoke the dbconsole: <tt>rails db</tt>.
 h4. +rails plugin+
 The +rails plugin+ command simplifies plugin management; think a miniature version of the Gem utility. Let's walk through installing a plugin. You can call the sub-command +discover+, which sifts through repositories looking for plugins, or call +source+ to add a specific repository of plugins, or you can specify the plugin location directly.
@@ -306,7 +312,7 @@ $ rails runner "Model.long_running_method"
 h4. +rails destroy+
-Think of +destroy+ as the opposite of +generate+. It'll figure out what generate did, and undo it. Believe you-me, the creation of this tutorial used this command many times!
+Think of +destroy+ as the opposite of +generate+. It'll figure out what generate did, and undo it.
 <shell>
 $ rails generate model Oops
@@ -333,9 +339,29 @@ $ rails destroy model Oops
     notempty  app
 </shell>
-h4. +rake about+
+h3. Rake
+Rake is Ruby Make, a standalone Ruby utility that replaces the Unix utility 'make', and uses a 'Rakefile' and +.rake+ files to build up a list of tasks. In Rails, Rake is used for common administration tasks, especially sophisticated ones that build off of each other.
+You can get a list of Rake tasks available to you, which will often depend on your current directory, by typing +rake --tasks+. Each task has a description, and should help you find the thing you need.
+<shell>
+$ rake --tasks
+(in /home/foobar/commandsapp)
+rake db:abort_if_pending_migrations       # Raises an error if there are pending migrations
+rake db:charset                           # Retrieves the charset for the current environment's database
+rake db:collation                         # Retrieves the collation for the current environment's database
+rake db:create                            # Create the database defined in config/database.yml for the current Rails.env
+...
+...
+rake tmp:pids:clear                       # Clears all files in tmp/pids
+rake tmp:sessions:clear                   # Clears all files in tmp/sessions
+rake tmp:sockets:clear                    # Clears all files in tmp/sockets
+</shell>
+h4. +about+
-Check it: Version numbers for Ruby, RubyGems, Rails, the Rails subcomponents, your application's folder, the current Rails environment name, your app's database adapter, and schema version! +about+ is useful when you need to ask for help, check if a security patch might affect you, or when you need some stats for an existing Rails installation.
+<tt>rake about</tt> gives information about version numbers for Ruby, RubyGems, Rails, the Rails subcomponents, your application's folder, the current Rails environment name, your app's database adapter, and schema version. It is useful when you need to ask for help, check if a security patch might affect you, or when you need some stats for an existing Rails installation.
 <shell>
 $ rake about
@@ -343,17 +369,55 @@ About your application's environment
 Ruby version              1.8.7 (x86_64-linux)
 RubyGems version          1.3.6
 Rack version              1.1
-Rails version             3.0.0
-Active Record version     3.0.0
-Action Pack version       3.0.0
-Active Resource version   3.0.0
-Action Mailer version     3.0.0
-Active Support version    3.0.0
+Rails version             3.1.0
+Active Record version     3.1.0
+Action Pack version       3.1.0
+Active Resource version   3.1.0
+Action Mailer version     3.1.0
+Active Support version    3.1.0
 Middleware                ActionDispatch::Static, Rack::Lock, Rack::Runtime, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::RemoteIp, Rack::Sendfile, ActionDispatch::Callbacks, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, Rack::MethodOverride, ActionDispatch::Head
 Application root          /home/foobar/commandsapp
 Environment               development
 </shell>
+h4. +assets+
+You can precompile the assets in <tt>app/assets</tt> using <tt>rake assets:precompile</tt> and remove compiled assets using <tt>rake assets:clean</tt>.
+h4. +db+
+The most common tasks of the +db:+ Rake namespace are +migrate+ and +create+, and it will pay off to try out all of the migration rake tasks (+up+, +down+, +redo+, +reset+). +rake db:version+ is useful when troubleshooting, telling you the current version of the database.
+h4. +doc+
+If you want to strip out or rebuild any of the Rails documentation (including this guide!), the +doc:+ namespace has the tools. Stripping documentation is mainly useful for slimming your codebase, like if you're writing a Rails application for an embedded platform.
+h4. +notes+
+These tasks will search through your code for commented lines beginning with "FIXME", "OPTIMIZE", "TODO", or any custom annotation (like XXX) and show you them.
+h4. +routes+
++rake routes+ will list all of your defined routes, which is useful for tracking down routing problems in your app, or giving you a good overview of the URLs in an app you're trying to get familiar with.
+h4. +test+
+INFO: A good description of unit testing in Rails is given in "A Guide to Testing Rails Applications":testing.html
+Rails comes with a test suite called Test::Unit. It is through the use of tests that Rails itself is so stable, and the slew of people working on Rails can prove that everything works as it should.
+The +test:+ namespace helps in running the different tests you will (hopefully!) write.
+h4. +tmp+
+The <tt>Rails.root/tmp</tt> directory is, like the *nix /tmp directory, the holding place for temporary files like sessions (if you're using a file store for files), process id files, and cached actions. The +tmp:+ namespace tasks will help you clear them if you need to if they've become overgrown, or create them in case of deletions gone awry.
+h4. Miscellaneous
+* +rake stats+ is great for looking at statistics on your code, displaying things like KLOCs (thousands of lines of code) and your code to test ratio.
+* +rake secret+ will give you a pseudo-random key to use for your session secret.
+* <tt>rake time:zones:all</tt> lists all the timezones Rails knows about.
 h3. The Rails Advanced Command Line
 More advanced use of the command line is focused around finding useful (even surprising at times) options in the utilities, and fitting those to your needs and specific work flow. Listed here are some tricks up Rails' sleeve.
@@ -437,7 +501,7 @@ Successfully installed mongrel-1.1.5
 Installing RDoc documentation for mongrel-1.1.5...
 $ rails server mongrel
 => Booting Mongrel (use 'rails server webrick' to force WEBrick)
-=> Rails 3.0.0 application starting on http://0.0.0.0:3000
+=> Rails 3.1.0 application starting on http://0.0.0.0:3000
 ...
 </shell>
@@ -534,60 +598,3 @@ I got assigned some args:
 </shell>
 Tada!
-h4. Rake is Ruby Make
-Rake is a standalone Ruby utility that replaces the Unix utility 'make', and uses a 'Rakefile' and +.rake+ files to build up a list of tasks. In Rails, Rake is used for common administration tasks, especially sophisticated ones that build off of each other.
-You can get a list of Rake tasks available to you, which will often depend on your current directory, by typing +rake --tasks+. Each task has a description, and should help you find the thing you need.
-<shell>
-$ rake --tasks
-(in /home/foobar/commandsapp)
-rake db:abort_if_pending_migrations       # Raises an error if there are pending migrations
-rake db:charset                           # Retrieves the charset for the current environment's database
-rake db:collation                         # Retrieves the collation for the current environment's database
-rake db:create                            # Create the database defined in config/database.yml for the current Rails.env
-...
-...
-rake tmp:pids:clear                       # Clears all files in tmp/pids
-rake tmp:sessions:clear                   # Clears all files in tmp/sessions
-rake tmp:sockets:clear                    # Clears all files in tmp/sockets
-</shell>
-h5. +db:+ Database
-The most common tasks of the +db:+ Rake namespace are +migrate+ and +create+, and it will pay off to try out all of the migration rake tasks (+up+, +down+, +redo+, +reset+). +rake db:version+ is useful when troubleshooting, telling you the current version of the database.
-h5. +doc:+ Documentation
-If you want to strip out or rebuild any of the Rails documentation (including this guide!), the +doc:+ namespace has the tools. Stripping documentation is mainly useful for slimming your codebase, like if you're writing a Rails application for an embedded platform.
-h5. +notes:+ Code note enumeration
-These tasks will search through your code for commented lines beginning with "FIXME", "OPTIMIZE", "TODO", or any custom annotation (like XXX) and show you them.
-h5. +test:+ Rails tests
-INFO: A good description of unit testing in Rails is given in "A Guide to Testing Rails Applications":testing.html
-Rails comes with a test suite called Test::Unit. It is through the use of tests that Rails itself is so stable, and the slew of people working on Rails can prove that everything works as it should.
-The +test:+ namespace helps in running the different tests you will (hopefully!) write.
-h5. +time:+ Timezones
-You can list all the timezones Rails knows about with +rake time:zones:all+, which is useful just in day-to-day life.
-h5. +tmp:+ Temporary files
-The tmp directory is, like in the *nix /tmp directory, the holding place for temporary files like sessions (if you're using a file store for files), process id files, and cached actions. The +tmp:+ namespace tasks will help you clear them if you need to if they've become overgrown, or create them in case of deletions gone awry.
-h5. Miscellaneous Tasks
- +rake stats+ is great for looking at statistics on your code, displaying things like KLOCs (thousands of lines of code) and your code to test ratio.
- +rake secret+ will give you a pseudo-random key to use for your session secret.
- +rake routes+ will list all of your defined routes, which is useful for tracking down routing problems in your app, or giving you a good overview of the URLs in an app you're trying to get familiar with.