defunkt

# If your workers are inactive for a long period of time, they'll lose
# their MySQL connection.
#
# This hack ensures we re-connect whenever a connection is
# lost. Because, really. why not?
#
# Stick this in RAILS_ROOT/config/initializers/connection_fix.rb (or somewhere similar)
#
# From:
#   http://coderrr.wordpress.com/2009/01/08/activerecord-threading-issues-and-resolutions/

cjohansen

/*
  Load Sinon.JS in the SpecRunner:

  <script type="text/javascript" src="lib/jasmine-1.0.1/jasmine.js"></script>
  <script type="text/javascript" src="lib/jasmine-1.0.1/jasmine-html.js"></script>
  <script type="text/javascript" src="sinon-1.0.0.js"></script>
  <script type="text/javascript" src="sinon-ie-1.0.0.js"></script>

  http://cjohansen.no/sinon/
*/

tenderlove

require 'test_helper'
require 'minitest/autorun'

module Tenderlove
  class Spec < MiniTest::Spec
    include ActiveSupport::Testing::SetupAndTeardown
    include ActiveRecord::TestFixtures

    alias :method_name :__name__ if defined? :__name__
    self.fixture_path = File.join(Rails.root, 'test', 'fixtures')

ramontayag

namespace :config do
  desc "Symlink the database config file from shared directory to current release directory."
  task :symlink_database_yml do
    run "ln -nsf #{shared_path}/config/database.yml #{release_path}/config/database.yml"
  end
  after 'deploy:update_code' , 'config:symlink_database_yml'
end

munhitsu

# In case you had some strange python installation
# NOTE: .pydistutils.cfg seems to be not compatible with brew install python
# areas I needed to clean before installation
# clean up ~/Library/Python
# clean up .local

# preconditions:
# xcode with command line tools installed
xcode-select --install

bryckbost

# env.rb
Capybara.register_driver :selenium do |app|
  Capybara::Selenium::Driver.new(app, :browser => :chrome)
end

Download chromedriver from http://code.google.com/p/selenium/downloads/list

mv chromedriver to /usr/local/bin so it's in your path.

jcasimir

Controller Filters

The Rails REST implementation dictates the default seven actions for your controllers, but frequently we want to share functionality across multiple actions or even across controllers. Controller filters are the easiest way to do that.

Before, After, and Around

There are three types of filters implemented in Rails:

• a before_filter runs before the controller action
• an after_filter runs after the controller action

cmhobbs

# this goes in lib/resque/failure/notifier.rb 

require 'resque/failure/multiple'
require 'resque/failure/redis'
require 'postmark'
require 'mail'

module Resque
  module Failure
    class Notifier < Base

sinisterchipmunk

Copyright (C) 2011 by Colin MacKenzie IV

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in

clooth

module ApplicationHelper
  def markdown(text, *renderer)
    case renderer[0]
    props = {
      hard_wrap:       true,
      gh_blockcode:    true,
      safe_links_only: true,
      filter_html:     true
    }
    when :authored