Joni Harker ConsoleCatzirl

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:

The problem

There's enough trouble with puppet's ssl model (mandatory client certs) that people go and do odd things to get around it. The primary problem is that for lab/preproduction environments, if you reinstall machines frequently, you lose access to the private key that generated the original cert but (absent some puppet cert --clean [node] operation) the cert still exists, leading to the dreaded Retrieved certificate doesn't match private key error.

A solution

Generate a single client certificate which all your nodes use, and have the master determine node names from facter rather than the SSL DN. This way you can re-install nodes with impunity and as long as your bootstrap plops down the correct config and the cert+key, you don't have any more SSL issues.

The caveats

If you have autosign turned on, this change represents a shift in security tradeoffs: you can turn off autosign and therefore more tightly control which clients can talk to your server because they need to have your clie

	#!/usr/bin/env ruby1.8

	class Workaround
	def initialize target_pid
	@target_pid = target_pid

	first_child
	end

	def first_child

	#!/bin/bash
	# A simple script to backup an organization's GitHub repositories.

	#-------------------------------------------------------------------------------
	# NOTES:
	#-------------------------------------------------------------------------------
	# * Under the heading "CONFIG" below you'll find a number of configuration
	# parameters that must be personalized for your GitHub account and org.
	# Replace the `<CHANGE-ME>` strings with the value described in the comments
	# (or overwrite those values at run-time by providing environment variables).

	cron { 'puppet':
	ensure => present,
	command => 'puppet agent --onetime --splay 60 --no-daemonize',
	minute => [ fqdn_rand(30), fqdn_rand(30) + 29 ],
	}

	# Example with basic types
	---
	hash:
	string: some text
	number: 12345
	array_of_bool: [on, off, true, false, yes, no]
	ruby symbol: :symbol
	array:
	- item one
	- item two

	#!/bin/sh

	# Do elasticsearch optimize on logstash previous day index
	# if $1 = all then optimize all indicies

	esindex="/opt/elasticsearch/data/elasticsearch/nodes/0/indices"
	# Grab yesterday's values
	D=`date +%d -d yesterday`
	M=`date +%m -d yesterday`
	Y=`date +%Y -d yesterday`

	for f in $(find $1 -iname "*.wsp"); do
	if [ -a $f ];
	then /opt/graphite/bin/whisper-set-aggregation-method.py $f max;
	fi;
	done