xaviershay/enki — pull request #47 by gevans (2012-01-22 18:47:54+00:00)
Title: Upgraded Enki to Rails 3.2.0

A couple days ago, [Rails 3.2.0 was released](http://weblog.rubyonrails.org/2012/1/20/rails-3-2-0-faster-dev-mode-routing-explain-queries-tagged-logger-store) with some awesome performance improvements over 3.1, making development a lot easier and faster.

I went through and upgraded various gems to the latest versions available, swapped out the exception_notification plugin with the gem, updated some configs, and reran the specs and features to ensure everything was passing. It all looks good on my end but let me know if you find something wrong.

## Asset pipeline

@dhh did an [awesome talk on the new asset pipeline](http://www.youtube.com/watch?v=cGdCI2HhfAU). Assets are now located in `app/assets` and `vendor/assets`. The vendor assets currently contain 3rd-party assets such as jQuery plugins. The rest is in the former path. You're also able to include assets from other gems (jQuery and Formtastic's stylesheet).

In production, these will be combined and minified into fewer files:

* `application.js`
* `application.css`
* `admin.js`
* `admin.css`

## A couple pitfalls

Well, not really, just something to look out for:

* This is the last release series that will support Ruby 1.8.7. Rails 4 will require Ruby 1.9.3 and above.

* You'll notice a couple warnings like so:

```
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/01/04/rails-3-2-0-rc2-has-been-released. (called from at /path/to/enki/Rakefile:7)
```

Another non-issue but something that will drive me nuts (I'll make another fix at some point). This warning is spit out for every plugin in `vendor/plugins` which is currently 3 times for acts_as_taggable_on_steroids, open_id_authentication, and verification.

That's about it for now. I hope this pull request helps.