See the full issue archive.
Subscribe to Ruby Weekly here.
Issue 144 - May 9, 2013
So reassured of its quality, the Phusion crew decided to leap straight to a more trustworthy 4.0.1 for the first stable release of Passenger 4, the popular Nginx and Apache deployment and server module for Rack apps.
With the recent release of Rails 4.0.0 Release Candidate 1, it's time to try it out and report any bugs. Here, Ryan Bates walks us through the steps to upgrade a Rails 3.2 application to Rails 4.0.
August 16-17, 2013 in Pittsburgh, PA.
Need to follow dependencies, but don't want to share your private source code? We agree with you! That's why we've created the “gemnasium” command line tool. Monitor your dependencies on gemnasium.com and get updates + security alerts, without granting access to your private repositories. It’s easy to setup, lightweight, and open-source. Keep your projects in shape!
An awesome slide deck from Sandi Metz (author of Practical Object-Oriented Design in Ruby) that offers simple, practical guidelines for choosing what to test and how to test it.
A discussion on the Ruby issue tracker about whether to deprecate supporting using '::' for calling methods (e.g.
An overview by James Coglan: "I’m going to explain how Ruby’s object system works, including method lookup, inheritance, super calls, classes, mixins, and singleton methods."
The first in a series of tutorials about building an iOS app using the Ruby-powered RubyMotion toolkit that then leans upon a Rails API on the backend.
A look at using jruby-complete (a way of packaging up your JRuby implementation along with your app for easier deploys) along with Bundler.
Rob McLarty presents a walkthrough of how he deployed a Rails 4 and Ruby 2-based app on a Ubuntu, Apache, Passenger and MySQL stack. There are 101 ways to do this; here's another.
The classic Structure and Interpretation of Computer Programs text rarely fails to inspire developers to try all sorts of clever trickery and in this case Google engineer Mingmin Xie has been inspired to implement lazy infinite streams. (Note that Ruby 2.0's lazy enumeration features will get you a lot of this too.)
Put common attributes in a single table, non-shared attributes in separate tables with foreign key references, and use object delegation so that each model transparently pulls what it needs from both.
A look at why the problem occurs and how to resolve it.
There's a good chance you're already using Postgres if you're building a Rails app. There's an even better chance you're not taking advantage of everything in it. These slides from RailsConf show you how to take advantage of some of its best features including arrays (tags), hstore (key-value), and full text search right from Rails.
Build better, faster Ruby on Rails apps with detailed error tracking and performance metrics. Compare hosts and track deploys, all from a single app. Try it 30 days for free; no credit card required.SPONSORED ITEM
Kickstarter engineer Aaron Suggs introduces Rack::Attack, a Rack middleware for throttling abusive requests that's actually used by the popular crowdfunding site.
Built on Sinatra. Has a nice visual design.
A processor for Paperclip that allows you to optimize and minify uploaded JPG, PNG or GIF images by wrapping around ImageOptim.
Our team is one of the largest Ruby on Rails teams in Sweden. We are a dozen developers passionate about delivering a great product. And we do. Join us.
CodeSchool has released ten videos about various Rails 4 features and techniques into the wild for us all to enjoy. They cover things like Turbolinks, caching, and ActiveRecord. No sign ups, direct MP4 links.
Address: Office 30, Lincoln Way, Fairfield Enterprise Centre, Louth, Lincs, UK, LN11 0LS