Garren garrensmith

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

Setting up fresh Ubuntu server for Rails

Preparations

$ sudo -i

Set preferred editor

$ export EDITOR=vim

In a perfect world, where things are done well, not just quickly, I would expect to find the following when joining the company:

Documentation

Accurate / up-to-date systems architecture diagram
Accurate / up-to-date network diagram
Out-of-hours support plan
Incident management plan

Recently, we've been working on extracting Ember conventions from applications we're working on into the framework. Our goal is to make it clearer how the parts of an Ember application work together, and how to organize and bootstrap your objects.

Routing

Routing is an important part of web applications. It allows your users to share the URL they see in their browser, and have the same things appear when their friends click on the link.

The Ember.js ecosystem has several great solutions for routing. But, since it is such an important part of most web applications, we've decided to build it right into the framework.

If you have already modeled your application state using Ember.StateManager, there are a few changes you'll need to make to enable routing. Once you've made those changes, you'll notice the browser's address bar spring to life as you start using your app—just by moving between states, Ember.js will update the URL automatically.

This gist is no longer valid. Please see Compass-Rails for instructions on how to install.

	type InitFunction func() (interface{}, error)

	type ConnectionPoolWrapper struct {
	size int
	conn chan interface{}
	}

	/**
	Call the init function size times. If the init function fails during any call, then
	the creation of the pool is considered a failure.

	#!/usr/bin/env bash

	# Usage: curl -L https://raw.github.com/gist/3277326/ubuntu_bootstrap.sh \| bash

	RUBY=1.9.3-p327

	echo "Updating Packages"; echo
	apt-get -y update && apt-get -y upgrade
	apt-get -y install build-essential zlib1g-dev libssl-dev libreadline6-dev libyaml-dev libgdbm-dev libxml2 libxml2-dev libxslt-dev git-core

	require "active_record"
	require "database_cleaner"
	require "rspec/rails/extensions"

	# Note that this will not load your Rails configuration which means things like
	# mass assignment protection by default, etc. will not be set.

	RSpec.configure do \|config\|
	config.before(:suite) do
	ActiveRecord::Base.configurations =

	A list of features that we want to see in CouchDB. Needs to be voted on so that it can become a priority queue.

	User Facing Features
	====================

	1. Conflicts are the rule, not the exception

	All previous versions of CouchDB hide conflicts by default (selecting
	an arbitrary but consistent winning revision). Expert users can find
	and resolve conflicts.

	%% @private
	-spec init(list()) -> {ok, {SupFlags::any(), [ChildSpec::any()]}} \|
	ignore \| {error, Reason::any()}.
	init([]) ->
	Dispatch = [
	%% {Host, list({Path, Handler, Opts})}
	{'_', [{[<<"graphs">>, graph], kw_handler, []}]}
	],

	RestartStrategy = one_for_one,