| #!/usr/bin/env ruby | |
| # gem 'pivotal-tracker' | |
| require 'pivotal-tracker' | |
| TRACKER_TOKEN = "..." | |
| TRACKER_PROJECT_ID = "..." | |
| PivotalTracker::Client.token = TRACKER_TOKEN | |
| PivotalTracker::Client.use_ssl = true |
This readme is a mixture of everything I read on SO+nokogiri wiki, which ultimately worked out for me.
Here are the steps which worked for me to get rid of segfaults with Nokogiri 1.4.4, on both Lion and Snow Leopard, with Ruby 1.8.7 (patchlevel 334 and +).
First diagnose which version of libxml2 you're using:
bundle exec nokogiri -v
If you have 2.7.3 listed somewhere, you're in bad waters (known to segfault). Install this:
HTTP is a stateless protocol. Sessions allow us to chain multiple requests together into a conversation between client and server.
Sessions should be an option of last resort. If there's no where else that the data can possibly go to achieve the desired functionality, only then should it be stored in the session. Sessions can be vulnerable to security threats from third parties, malicious users, and can cause scaling problems.
That doesn't mean we can't use sessions, but we should only use them where necessary.
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.
| if Rails.env.features? || Rails.env.test? | |
| ActiveRecord::Base.class_eval do | |
| class << self | |
| def delete_all_of_all | |
| @model_subclasses_for_delete_all_of_all.each do |klass| | |
| klass.delete_all | |
| end | |
| end | |
| def inherited_with_model_tracker(subclass) | |
| @model_subclasses_for_delete_all_of_all ||= [] |