nicolasblanco

The gems I use on almost all my projects (because today is Friday... if you know what I mean)

• kaminari

  Great pagination gem. I like writing my custom paginators as partials instead of Ruby classes.

• rails_config

Even if there's "rails" in the name, this gem also works with other frameworks. Essential to have a global configuration object available everywhere in your app. I like the fact that it is environment-aware.

gogogarrett

class ArtistsController < ApplicationController

  def create
    @form = create_new_form
    workflow = Workflows::ArtistWorkflow.new(@form, params[:artist])

    workflow.process do |obj|
      return respond_with obj
    end
    render :new

thbar

Despite existing checks in the gem, I want to make sure it's not possible to activate better_errors at all in production (eg: erroneous RAILS_ENV configuration set to development, etc).

Here better_errors should be activated only if a .use_better_errors file is in place and if I'm on Mac OS X.

Not sure if this is necessary given the existing checks in the gem, but I suspect it cannot hurt either.

Next step: find a way to avoid putting them in the Gemfile completely.

brunobord

/**
 * Casper script to restart Alwaysdata processes.
 *
 * Usage:
 * $ casperjs kill.js email@example.com mysecretpassword
 */
var casper = require('casper').create();

casper.start("https://admin.alwaysdata.com/login/");

bf4

List moved

Please use https://github.com/bf4/learning to fork and pull changes.

thbar

<%
  # http://mislav.uniqpath.com/rails/branching-the-database-along-with-your-code/
  branch = `git symbolic-ref HEAD 2>/dev/null`.chomp.sub('refs/heads/', '')
  suffix = `git config --bool branch.#{branch}.database`.chomp == 'true' ? "_#{branch}" : ""
%>

common: &common
  adapter: mysql2
  encoding: utf8
  pool: 5

ryanb

My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.

A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.

You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.

class Article < ActiveRecord::Base

kaelig

This gist demonstrates how to use Compass magic sprites in combination with HiDPI.

See how it's done

Credits: Images ©BBC News.

mperham

class ActiveRecord::Base
  mattr_accessor :shared_connection
  @@shared_connection = nil

  def self.connection
    @@shared_connection || ConnectionPool::Wrapper.new(:size => 1) { retrieve_connection }
  end
end
ActiveRecord::Base.shared_connection = ActiveRecord::Base.connection

bluemont

class UrlValidator < ActiveModel::EachValidator

  def validate_each(record, attribute, value)
    valid = begin
      URI.parse(value).kind_of?(URI::HTTP)
    rescue URI::InvalidURIError
      false
    end
    unless valid
      record.errors[attribute] << (options[:message] || "is an invalid URL")