Rails in a Nutshell manuscript now available for collaboration

Posted on October 21st, 2009 by cody |0 comments » | Filed in Announcements, Rails

I'm excited to announce that the manuscript of Rails in a Nutshell is now available in draft format through the O'Reilly Open Feedback Publishing System (OFPS).

Rails in a Nutshell on OFPS

Rails in a Nutshell aims to be the perfect desktop companion for your Rails 3.0 development by providing condensed referenced material and tips.

We decided to release the book through the O'Reilly Open Feedback System so that you can read the manuscript while it is in progress and help create exactly the book you want. Consider it an agile process for book writing. We can incorporate your feedback and correct errors much more quickly before the book hits printers.

We're aiming to have the book ready for the launch of Rails 3.0. I strongly encourage you to check out the current draft and provide any feedback or comments you might have.

You can follow the progress of the book on Twitter via twitter.com/railsnutshell..

Jump Start Credit Card Processing Guide

Posted on January 13th, 2009 by cody | Filed in Announcements, Rails, Ruby

Jump Start Credit Card Processing

The makers of Freckle Time Tracking have created a beautiful and informative guide about getting started with Active Merchant called Jump Start Credit Card Processing. The guide is free to download and jam packed with information and great design. There is even a checklist for getting a merchant account near the end, which will definitely easy the pain of getting started.





Rails HTTP Status Code to Symbol Mapping

Posted on July 4th, 2008 by cody | Filed in Rails

Recently I had been wondering what the complete list of HTTP status code symbols was in Rails. Searching through Rails didn't yield any results for a symbol like :unprocessable_entity. Digging around in the Rails source code I found the file actionpack/lib/action_controller/status_codes.rb, which has the mapping of the status code to the status message. Then Rails defines the symbol to status code mapping dynamically from the status message.

The symbol used is an underscored version of the status message with no spaces. A quick Ruby script yields the following mapping:

Status CodeStatus MessageSymbol
1xx Informational
100Continue:continue
101Switching Protocols:switching_protocols
102Processing:processing
 
2xx Success
200OK:ok
201Created:created
202Accepted:accepted
203Non-Authoritative Information:non_authoritative_information
204No Content:no_content
205Reset Content:reset_content
206Partial Content:partial_content
207Multi-Status:multi_status
226IM Used:im_used
 
3xx Redirection
300Multiple Choices:multiple_choices
301Moved Permanently:moved_permanently
302Found:found
303See Other:see_other
304Not Modified:not_modified
305Use Proxy:use_proxy
307Temporary Redirect:temporary_redirect
 
4xx Client Error
400Bad Request:bad_request
401Unauthorized:unauthorized
402Payment Required:payment_required
403Forbidden:forbidden
404Not Found:not_found
405Method Not Allowed:method_not_allowed
406Not Acceptable:not_acceptable
407Proxy Authentication Required:proxy_authentication_required
408Request Timeout:request_timeout
409Conflict:conflict
410Gone:gone
411Length Required:length_required
412Precondition Failed:precondition_failed
413Request Entity Too Large:request_entity_too_large
414Request-URI Too Long:request_uri_too_long
415Unsupported Media Type:unsupported_media_type
416Requested Range Not Satisfiable:requested_range_not_satisfiable
417Expectation Failed:expectation_failed
422Unprocessable Entity:unprocessable_entity
423Locked:locked
424Failed Dependency:failed_dependency
426Upgrade Required:upgrade_required
 
5xx Server Error
500Internal Server Error:internal_server_error
501Not Implemented:not_implemented
502Bad Gateway:bad_gateway
503Service Unavailable:service_unavailable
504Gateway Timeout:gateway_timeout
505HTTP Version Not Supported:http_version_not_supported
507Insufficient Storage:insufficient_storage
510Not Extended:not_extended

Update

The cheat gem contains a cheat sheet for the status codes. You can get the gem and view the status codes as follows:


sudo gem install cheat
cheat status_codes

Thanks for the info Josh.