purcell

  # Based on https://gist.github.com/1182136
  class BootstrapLinkRenderer < ::WillPaginate::ActionView::LinkRenderer
    protected

    def html_container(html)
      tag :div, tag(:ul, html), container_attributes
    end

    def page_number(page)
      tag :li, link(page, page, :rel => rel_value(page)), :class => ('active' if page == current_page)

bbonamin

#app/models/event.rb

class Event < ActiveRecord::Base
  translates :title, :description
  has_many :event_translations
  accepts_nested_attributes_for :event_translations, :allow_destroy => true

end

john-patrik

source 'https://rubygems.org'

ruby '1.9.3'
gem 'rails', '3.2.11'
gem 'thin'

gem 'jquery-rails'
gem 'active_link_to'

group :assets do

masonforest

Installing a Gem on Heroku from a Private GitHub Repo

Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.

Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.

1. Get an OAuth Token from GitHub

---

First you will need to get an OAuth Token from GitHub using your own username and "note"

jrochkind

######################
#
#  Monkey patch to ActiveRecord to prevent 'implicit' checkouts. Currently tested with Rails 4.0.8, prob
#  should work fine in Rails 4.1 too. 
#
#  If you create a thread yourself, if it uses ActiveRecord objects without
#  explicitly checking out a connection, one will still be checked out implicitly.
#  If it is never checked back in with `ActiveRecord::Base.clear_active_connections!`,
#  then it will be leaked. 
#