diff options
author | Sebastian Martinez <sebastian@wyeworks.com> | 2011-05-25 20:03:06 -0300 |
---|---|---|
committer | Sebastian Martinez <sebastian@wyeworks.com> | 2011-05-25 20:03:06 -0300 |
commit | 0f7a52d920319842d45351b2e489b281a76b682a (patch) | |
tree | b5fba327e2504d1b47f55d015e1bc41c3d176848 | |
parent | b7921f50e7cb08bbfddacbcc46b22dc74738cc5c (diff) | |
download | rails-0f7a52d920319842d45351b2e489b281a76b682a.tar.gz rails-0f7a52d920319842d45351b2e489b281a76b682a.tar.bz2 rails-0f7a52d920319842d45351b2e489b281a76b682a.zip |
Fix fixed-fonts stlye on rails_on_rack guide.
-rw-r--r-- | railties/guides/source/initialization.textile | 14 | ||||
-rw-r--r-- | railties/guides/source/rails_on_rack.textile | 12 |
2 files changed, 13 insertions, 13 deletions
diff --git a/railties/guides/source/initialization.textile b/railties/guides/source/initialization.textile index 638830cd83..e4da77eee1 100644 --- a/railties/guides/source/initialization.textile +++ b/railties/guides/source/initialization.textile @@ -155,13 +155,13 @@ h4. +config/boot.rb+ In a standard Rails application, there's a +Gemfile+ which declares all dependencies of the application. +config/boot.rb+ sets +ENV["BUNDLE_GEMFILE"]+ to the location of this file, then requires Bundler and calls +Bundler.setup+ which adds the dependencies of the application (including all the Rails parts) to the load path, making them available for the application to load. The gems that a Rails 3.1 application depends on are as follows: * abstract (1.0.0) -* actionmailer (3.1.0.beta) -* actionpack (3.1.0.beta) -* activemodel (3.1.0.beta) -* activerecord (3.1.0.beta) -* activeresource (3.1.0.beta) -* activesupport (3.1.0.beta) -* arel (2.0.7) +* actionmailer (3.1.0.rc1) +* actionpack (3.1.0.rc1) +* activemodel (3.1.0.rc1) +* activerecord (3.1.0.rc1) +* activeresource (3.1.0.rc1) +* activesupport (3.1.0.rc1) +* arel (2.1.0) * builder (3.0.0) * bundler (1.0.6) * erubis (2.6.6) diff --git a/railties/guides/source/rails_on_rack.textile b/railties/guides/source/rails_on_rack.textile index aa53aa6db6..8d5985dba8 100644 --- a/railties/guides/source/rails_on_rack.textile +++ b/railties/guides/source/rails_on_rack.textile @@ -111,11 +111,11 @@ h5. Adding a Middleware You can add a new middleware to the middleware stack using any of the following methods: -* +config.middleware.use(new_middleware, args)+ - Adds the new middleware at the bottom of the middleware stack. +* <tt>config.middleware.use(new_middleware, args)</tt> - Adds the new middleware at the bottom of the middleware stack. -* +config.middleware.insert_before(existing_middleware, new_middleware, args)+ - Adds the new middleware before the specified existing middleware in the middleware stack. +* <tt>config.middleware.insert_before(existing_middleware, new_middleware, args)</tt> - Adds the new middleware before the specified existing middleware in the middleware stack. -* +config.middleware.insert_after(existing_middleware, new_middleware, args)+ - Adds the new middleware after the specified existing middleware in the middleware stack. +* <tt>config.middleware.insert_after(existing_middleware, new_middleware, args)</tt> - Adds the new middleware after the specified existing middleware in the middleware stack. <ruby> # config/environment.rb @@ -154,20 +154,20 @@ h4. Internal Middleware Stack Much of Action Controller's functionality is implemented as Middlewares. The following table explains the purpose of each of them: |_.Middleware|_.Purpose| -|+Rack::Lock+|Sets +env["rack.multithread"]+ flag to +true+ and wraps the application within a Mutex.| +|+Rack::Lock+|Sets <tt>env["rack.multithread"]</tt> flag to +true+ and wraps the application within a Mutex.| |+ActionController::Failsafe+|Returns HTTP Status +500+ to the client if an exception gets raised while dispatching.| |+ActiveRecord::QueryCache+|Enables the Active Record query cache.| |+ActionController::Session::CookieStore+|Uses the cookie based session store.| |+ActionController::Session::MemCacheStore+|Uses the memcached based session store.| |+ActiveRecord::SessionStore+|Uses the database based session store.| -|+Rack::MethodOverride+|Sets HTTP method based on +_method+ parameter or +env["HTTP_X_HTTP_METHOD_OVERRIDE"]+.| +|+Rack::MethodOverride+|Sets HTTP method based on +_method+ parameter or <tt>env["HTTP_X_HTTP_METHOD_OVERRIDE"]</tt>.| |+Rack::Head+|Discards the response body if the client sends a +HEAD+ request.| TIP: It's possible to use any of the above middlewares in your custom Rack stack. h4. Customizing Internal Middleware Stack -It's possible to replace the entire middleware stack with a custom stack using +ActionController::Dispatcher.middleware=+. +It's possible to replace the entire middleware stack with a custom stack using <tt>ActionController::Dispatcher.middleware=</tt>. Put the following in an initializer: |