scrogson

# config/initializers/sandbox_email_interceptor.rb
ActionMailer::Base.register_interceptor(SandboxEmailInterceptor) unless Rails.env.production?

stephencelis

# More "proper" than a miniskirt (http://gist.github.com/273579).
class Minidress
  @@factories = {}
  class << self
    def define(name, &block)
      @@factories[name.to_s] = block
    end

    def build(name, attrs = {})
      new(name.to_s.classify.constantize.new, &@@factories[name.to_s]).record

josevalim

# = YERB
#
# Who needs HAML when you have YAML + ERB? ;)
#
# See example.yaml below for an example. You can run this code
# by cloning this gist and then `ruby _yerb.rb example.yaml`.
#
# Notice that you need Ruby 1.9 so the hash order is preserved.
# Obviously, this is just for fun. Definitely slow as hell.
#

galtenberg

# More "proper" than a miniskirt (http://gist.github.com/273579).
class Minidress
  @@factories = {}
  class << self
    def define(name, &block)
      @@factories[name.to_s] = block
    end

    def build(name, attrs = {})
      new(name.to_s.classify.constantize.new, &@@factories[name.to_s]).record

galtenberg

# Factory girl, relaxed.
#
#   Factory.define :user do |f|
#     f.login 'johndoe%d'                          # Sequence.
#     f.email '%{login}@example.com'               # Interpolate.
#     f.password f.password_confirmation('foobar') # Chain.
#   end
#
#   Factory.define :post do |f|
#     f.user { Factory :user }                     # Blocks, if you must.

cavalle

Cohesion and Big ActiveRecord Models

One of the problems of big ActiveRecord models is their low cohesion. In Rails we group behaviour around the entities of the domain we're modelling. If we use only ActiveRecord models for that, we'll probably end up with classes full of actions, in most cases, completely unrelated to each other (except for the fact that they act on the same domain entity).

To illustrate the issue let's imagine a big Post AR model of a blog application. In this app, users can add tags to their posts. Since this is the only class with this ability, I decide to put the related logic in the Post model itself. For this, presumably at the beginning of the file, I write a couple of has_many entries for tags and taggings. Then, fifty lines below, along with the rest of scopes, I add one more to find posts by tag name. A couple of hundred lines later, I put a virtual attribute tag_list which will be used to update the associations from a string of tag names separated by commas. Fin

swistak35

# Firstly, install gems: 'evilr' and 'include'

# Example with User in a shop application.
# He has two roles
#   - buyer (with money on the account and so on)
#   - reviewer (he can review books he bought)


require 'evilr'
require 'include'

sentientmonkey

#!/usr/bin/env ruby

require 'logger'

# rotatelogs required...
# http://httpd.apache.org/docs/2.2/programs/rotatelogs.html
logger = Logger.new("|rotatelogs ./foo.log.%Y-%m-%d-%H 3600", 0, 0)

10.times do 
  logger.error "testing..."

thbar

require 'childprocess'

guard 'shell' do
  watch %r{^app/(.+)\.rb$} do |m|
    `killall rake`

    # Why this:
    # - spawn a child process to avoid locking Guard
    # - make sure that the child process has stdout and stdin otherwise it crashes
    # - bonus point: get REPL access in the simulator!

gustafnk

var poll = function(){ 
  window.scrollTo(0, document.body.scrollHeight);
  setTimeout(function(){ poll() }, 500);
};

poll();