| # bash completion for rake | |
| # | |
| # some code from on Jonathan Palardy's http://technotales.wordpress.com/2009/09/18/rake-completion-cache/ | |
| # and http://pastie.org/217324 found http://ragonrails.com/post/38905212/rake-bash-completion-ftw | |
| # | |
| # For details and discussion | |
| # http://turadg.aleahmad.net/2011/02/bash-completion-for-rake-tasks/ | |
| # | |
| # INSTALL | |
| # |
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.
| require "uri" | |
| (URI::REGEXP.constants - ["PATTERN"]).each do |rc| | |
| puts "#{rc}: #{URI::REGEXP.const_get(rc)}" | |
| end | |
| URI::REGEXP::PATTERN.constants.each do |pc| | |
| puts "#{pc}: #{URI::REGEXP::PATTERN.const_get(pc)}" | |
| end |
The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.
You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.
A Dashing widget that checks whether a server is responding to either an http or ping request. It displays either a check or alert depending on the response.
