MicahElliott

Setting up and installing rbenv, ruby-build, rubies, rbenv-gemset, and bundler

This guide enables you to install (ruby-build) and use (rbenv) multiple versions of ruby, isolate project gems (gemsets and/or bundler), and automatically use appropriate combinations of rubies and gems.

TL;DR Demo

# Ensure system is in ship-shape.

aptitude install git zsh libssl-dev zlib1g-dev libreadline-dev libyaml-dev

aspyct

# Sample implementation of quicksort and mergesort in ruby
# Both algorithm sort in O(n * lg(n)) time
# Quicksort works inplace, where mergesort works in a new array

def quicksort(array, from=0, to=nil)
    if to == nil
        # Sort the whole array, by default
        to = array.count - 1
    end

stereoscott

class ApplicationController < ActionController::Base
  before_filter :prepend_view_path_if_mobile
  
  def mobile_request?
    @mobile_request ||= (request.subdomains.first == domain_prefixes[:mobile])
  end
  helper_method :mobile_request?
    
  def prepend_view_path_if_mobile
    prepend_view_path Rails.root + 'app' + 'views_mobile' if mobile_request?

codespore

# Add Action button on the top navigation menu. Useful for resource with nested resources

action_item :only => :show do
  link_to('Show Users', admin_group_users_path(resource))
end


# Custom show page with children items

show do

justinweiss

# Call scopes directly from your URL params:
#
#     @products = Product.filter(params.slice(:status, :location, :starts_with))
module Filterable
  extend ActiveSupport::Concern

  module ClassMethods
    
    # Call the class methods with names based on the keys in <tt>filtering_params</tt>
    # with their associated values. For example, "{ status: 'delayed' }" would call 

DanHerbert

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.

danchoi

#!/bin/bash

# deploy.sh

# Put this script on your production server and make it executable with chmod
# +x. 

# Set the deploy_dir variable to the path on the production server to
# deployment directory. The script assumes the deployment directory is a git
# clone of the codebase from an upstream git repo. This script also assumes

tadast

# 1) Create your private key (any password will do, we remove it below)

$ cd ~/.ssh
$ openssl genrsa -des3 -out server.orig.key 2048


# 2) Remove the password

$ openssl rsa -in server.orig.key -out server.key

gcarrion-gfrmedia

# Install Git needed for Git based gems
packages:
  yum:
    git: []
    

coderberry

require 'oauth'
require 'httpclient'
require 'json'

class SimpleTwitter
  def initialize(config)
    @config = config
    @http_client = HTTPClient.new
  end