Matt Button BRMatt

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 = [email protected]: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:

Upload Travis CI builds to S3

This will demonstrate how to upload build files from Travis CI to S3.

NOTE: Keys have been changed to protect the innocent.

Step 1: Create an S3 policy.

Create an S3 ACL policy, see s3_policy.json for an example.

A Continuous Packaging Pipeline

A list of tools mentioned in my Ignite talk from Devopsdays Rome 2012 on a continuous packaging pipeline, with links and short description for each tool.

The talk slides are at https://speakerdeck.com/mpasternacki/a-continuous-packaging-pipeline; a longer blog post will be written soon.

Vendorificator

Available at https://github.com/3ofcoins/vendorificator/ or with gem install vendorificator

Include third party modules in your git repo, using pristine branches to sanely maintain local changes, upgrades, and merges.

Changes:

this version includes backport of Greg Price's patch for speedup startup http://bugs.ruby-lang.org/issues/7158 .

ruby-core prefers his way to do thing, so that I abandon cached-lp and sorted-lf patches of mine.
this version integrates 'array as queue' patch, which improves performance when push/shift pattern is heavily used on Array.

This patch is accepted into trunk for Ruby 2.0 and last possible bug is found by Yui Naruse. It is used in production* for a couple of months without issues even with this bug.

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 &lt; ActiveRecord::Base

Models, Roles, Decorators, and Interactions

A modest alternative to DCI that might be worth further thought

One of the problems with advancing the discussion on DCI is that we lack a comparable alternative pattern that has the same goals, but favors a low ceremony approach. The closest thing we have to that is Rails concerns, but they are more like distant relatives of the DCI concepts rather than first cousins, and that makes comparisions between the two approaches not especially fruitful.

I am considering the idea of experimenting with my own paradigm that captures the intent and purity of DCI, but with the convenience of concerns. Please note that this is just the starting point of a conversation, it is NOT a promise of comercially available cold fusion or a cure for cancer. It's just a gist with an idea on it I'd like to hear your thoughts on.

What if we had a top-level topology that was split into Models, **Rol

	# SSL self signed localhost for rails start to finish, no red warnings.

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

	$ openssl genrsa -des3 -out server.orig.key 2048


	# 2) Remove the password

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

	# define a method to run rake tasks
	def run_rake(task, options={}, &block)
	rake = fetch(:rake, 'rake')
	rails_env = fetch(:rails_env, 'production')

	command = "cd #{current_path} && #{rake} #{task} RAILS_ENV=#{rails_env}"
	run(command, options, &block)
	end

	// In this example we detect if a user clicks a link to travel elsewhere
	// but has made changes to a form. If they have changed the form it prompts
	// them to confirm before continuing.
	jQuery(function ($) {
	var $form = $('form').watchChanges();

	$('a').click(function (e) {
	if ($form.hasChanged() and ! confirm('Continue without saving changes?')) {
	e.preventDefault();
	}

	#! /usr/bin/env python
	from boto.ses.connection import SESConnection
	import os
	import sys
	import subprocess
	import socket

	TMPFILE = '/var/run/postgresql/last-wal-archive-error-file.tmp'

	if __name__ == '__main__':