rake middleware not working in rails3 beta 3

The issue here is that rake tasks do not necessarily initialize your application. I.e. They load config/application but may not load config/environment or any of the initializers unless explicitly asked.

That said, you should add the middleware to your app inside config/application.

However there is always the chance this problem will happen in other circumtances, so the long term fix would make rake middleware always load the environment. The downside is the task becomes slower.

Jeremy, wdyt?

I've moved it to config/application.rb, and now I see the stack. Thnx.

The reason I'd put it in environment.rb is because that's what's being advertised everywhere I looked (e.g. http://guides.rails.info/rails_on_rack.html and http://asciicasts.com/episodes/151-rack-middleware).

I can imagine wanting middlewares that are only used within e.g. environments/development.rb. I think it would be good if you could see the complete stack then too. A slower task isn't an issue, displaying correct information is, imo.

If you put in environments/development.rb it will still work. It won't work if you add them in any of config/initializers/* and config/environment.rb. And I totally agree that displaying correct information should be the priority.

+1 to loading the env

Actually, rails was loading the environment, but rake tasks were doing it by itself (calling Rails::Application.initialize!) instead of loading the file at config/environment.rb. This was probably also the cause some rake tasks were loading the environment twice. A patch is coming soon.