I have been playing around with RESTful Rails recently. Below is my collection or Rails REST howtos, tutorials and other resources I have found so far.

ObjectiveResource is an Objective-C port of Ruby on Rails' ActiveResource. It provides a way to serialize objects to and from Rails' standard RESTful web-services (via XML or JSON) and handles much of the complexity involved with invoking web-services of any language from the iPhone.

There are many wonderful things about Rails and the Rails ecosystem. A clean, well-lighted path for keeping all your extensions up to date is not one of them.

RubyGems 1.6.0 can break Rails 2.x with ActiveSupport::Dependencies::Mutex NameError during startup; loading thread before boot.rb prevents the failure.

Rails models expose callback chains for save events, making it possible to inspect registered before and after methods and identify method names.

Refile is a Rails gem for file uploads with better direct-to-S3 support than CarrierWave, but on-demand image rendering can increase server load and require caching or a CDN.

Check a gem’s release history to find newer compatible versions, especially when you need a Rails 2 variant of an installed library.

Database query limits prevent runaway SQL from consuming all resources; PostgreSQL statement_timeout and MySQL max_execution_time can cancel slow statements automatically.

rack-mini-profiler helps spot slow Rack and Rails requests by measuring SQL queries, memory allocation, and CPU time.

Untangling JavaScript spaghetti in Rails front ends by splitting responsibilities into separate layers without a JavaScript framework.

Rails 4 no longer needs the :assets Gemfile group because production no longer triggers unwanted on-demand asset compilation.

Delayed background jobs can run before a Rails record is committed, causing after_save logic to see unsaved state and fail unexpectedly.

Rails 3 can now save records without running callbacks, reducing side effects when callbacks should be bypassed.

Exception tracking service for any platform with a Rails notifier and REST API, useful as a free alternative to Hoptoad/Airbrake for custom error reporting.

E2E tests often fail from race conditions between browser, app, and test script; synchronizing actions, retries, and test environment settings improves stability.

Selective Rails migrations can be moved up, down, redone, or targeted by version instead of processing the full sequence.

Conditional Rails validations with if: are not covered by Shoulda Matchers; test the model’s behavior by stubbing the predicate and checking presence only when it applies.

Large legacy data migrations need deep source-system understanding, fast failure, dedicated logging, and traceable migration metadata to keep long-running imports debuggable and verifiable.

Rails AssociationTypeMismatch errors often come from selecting an associated object instead of its ID in a form field.

Test-only routes can help verify redirects and other edge cases without changing the normal route set. with_routing replaces existing routes, so evaluating a route block keeps both sets available.

JSON responses can be reused in legacy cross-domain requests by wrapping them in a callback function. rack-contrib provides a JSONP middleware for Rails apps.

Testing a gem across Rails versions is easier with shared app code and specs via symlinks, keeping one test setup aligned with current best practice.

query_diet now works with Rails 3, with installation differing slightly from older versions.

A profile of _why and his influence on Ruby and Ruby on Rails, with a personal angle that makes programming culture approachable for nontechnical readers.