Enable warnings from tests.
Move require for 'rails/version' to the file that needs it
Adds protected_instance_variables to ActionController::API for compatibitlity with some gems and Rails 4.1
change rails three stack method name
Added whitelisting of params on generate action
Update README.md
Merge pull request #149 from shazadmaved/patch-1

Update README.md
Merge pull request #145 from buddhamagnet/baby-steps

Change rails three stack method name
Merge pull request #144 from edowling/master

Adds self.protected_instance_variables to ActionController::API
Merge pull request #125 from vipulnsward/enable-warnings

Enable warnings from tests.
Merge pull request #124 from ReneB/fix_require_version

Move require for 'rails/version' to the file that needs it
Use the new Docker queue

faster better stronger
small change so the proper queue is picked up corectly
Merge pull request #152 from joshk/patch-1

Use the new Docker queue
Adding info on removing protect_from_forgery to readme.

The implications of removing `protect_from_forgery` aren't made clear, which might be a big deal for the average user who likely relies on Rails to know best when it comes to things like authentication. 

I can imagine there being a bunch of sites using rails-api with cookie-based auth and CSRF turned off. If using cookie-based auth is a requirement, there are workarounds for to inject CSRF headers into AJAX requests. 

It's not really a simple issue, so I tried adding a question to the readme that would make the potential user investigate. It's also possible that it might make more sense to just link to information about token-based authentication, which I'd assume is what's typically used with APIs.
Merge pull request #153 from dgsan/patch-1

Adding info on removing protect_from_forgery to readme.
Merge pull request #148 from txdavidtx/controller_params_whitelisting

Added whitelisting of params on generate action
Merge pull request #1 from rails-api/master

merge other junk into mine