| #!/bin/sh | |
| ### BEGIN INIT INFO | |
| # Provides: delayed_job | |
| # Required-Start: $all | |
| # Required-Stop: $local_fs $syslog | |
| # Default-Start: 2 3 4 5 | |
| # Default-Stop: 0 1 6 | |
| # Short-Description: starts the delayed_job instances | |
| # Description: starts the delayed_job server instances using start-stop-daemon | |
| # |
| # Requires Ruby 1.9 and OS X | |
| # The letters in your game... include repeats | |
| game_letters = %w() | |
| # Words that have been played already | |
| played = %w() | |
| def to_hash(letters) | |
| letters.inject({}) do |h,l| | |
| h[l] ||= 0 |
| # For context, this was inspired by the RubyRogues podcast #79 where they talked about | |
| # documentation in Ruby, and specifically grumbled quite a bit about the failings of RDoc. | |
| # | |
| # http://rubyrogues.com/079-rr-documenting-code/ | |
| # | |
| # As someone who's spent a lot of time using an IDE for programming C# and Java, I think | |
| # Ruby could do a lot better at putting documentation at our fingertips as we program. | |
| # | |
| # Maybe making the documentation part of the structure of the code would facilitate this? | |
| # |
| // Backbone.js 0.9.1 | |
| // (c) 2010-2012 Jeremy Ashkenas, DocumentCloud Inc. | |
| // Backbone may be freely distributed under the MIT license. | |
| // For all details and documentation: | |
| // http://backbonejs.org | |
| // | |
| // HACKED TO BE PROTOTYPE.JS COMPATIBLE BY [SUBIMAGE AT GMAIL DOT COM] | |
| // REQUIRES PROTOTYPE >= 1.7.1 | |
| // !!! TODO needs tests! |
By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:
/people/6
But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.