5:44 Play Subscribe with or Intro song by Falseta

Episode #40 - January 8, 2010

2416793a63b63c656da7f264db907297.jpg?s=18&r=pg&d=http%3a%2f%2fwww.gravatar.com%2favatar%2f8ebf4339f7c8cd73b53d1d1d3eba7c35 Jim Hoskins 3ac3c66144bb3f7330af9fb6ab64d8a2.jpg?s=18&r=pg&d=http%3a%2f%2fwww.gravatar.com%2favatar%2f8ebf4339f7c8cd73b53d1d1d3eba7c35 Nick Pettit

Cramp, Validation Scopes, and Weary are covered in this Friday episode. We also talk about password security without SSL, Bonsai, and how to use Jekyll on Heroku.

Subscribe to our mailing list!

This episode is sponsored by Heroku. Instantly deploy and scale your Ruby application.

  • Heroku
  • Cramp
  • Password Security
  • Validation Scopes
  • Weary
  • Bonsai
  • Jekyll
  • Ruby5

Jekyll on Heroku Jump to Story

A few weeks ago, we talked about rack-jekyll, which was a way to use Jekyll, the static site generator, on Rack. Jesse Storimer wrote in about the story, and said that he tried using it but it failed to publish his Jekyll blog. So in response to this, he decided to take the initiative to write about how he’s posting his Jekyll blog to Heroku.

April 18th, 2014

URL parsing with Rippersnapper, awesome APIs with Pliny, thread-safe utilities from Charles Nutter, a revival of the invoicing gem, info about recursion and memoization, querying git with gitql, and refactoring bad controllers all in this episode of the Ruby5 podcast!

April 15th, 2014

In this episode we cover the results of the Cloudflare Heartbleed challenge, tracking trends in the Ruby community with the Ruby Survey, Rails 4.1 ActiveRecord enums, iStats for CPU temperature on OS X and some Insanely Useful ActiveAdmin Customizations.

April 8th, 2014

The internet is heartbleeding plus exciting rails 4.1 features. With special guest Nathan Hessler.

April 8th, 2014

On today's episode: Rails 4 PostgreSQL integration, tips for hiring great software engineers, Ruby Love, what your conference proposal is missing, crafting a conference talk, an introduction to JSON schemas, Build a Ruby Gem, and Surviving APIs with Rails