Mark Hughes greenantdotcom

Purpose

I understand why we would want to have the database be queried if we have, say, a cache Miss/Mrs./Ms. or a cache-hard-down, but I would suggest a more Interface-oriented/Compositional approach, like the below which may end up being more testable and with a consistent interface for cients.

Fork of https://gist.github.com/1071989
Further CentOS 5.x instructions customized by MJH

Ideally do this as SUDO

yum install -y git gcc gcc-c++ zlib-devel curl curl-devel openssl

Install node

TK - replace with nodejs-stable YUM instructions

Say you're on a branch named BEFOURE-310 and you want to fix the typo. Renaming the branch is this simple:

git br --move BEFOUR-310

Why?

When working on a remote machine, or a machine that doesn't have a GUI plist editor on it, the command line may be your only or best option.

There are two options present on OS X to help you.

`default`

Using the default command on OS X can help you get around.

Alternatively, in the Amazon interface, you can select a directory or file, and click on the action "Mark as public"

	input {
	file {
	type => syslog
	path => "/var/log/messages"
	}
	}

	filter {
	grok {
	type => syslog

	### View a key's information

	openssl rsa -in key -noout -modulus

	### View a CSR's information

	openssl req -in csr -noout -modulus

	### View a certificate's information

	###
	### DO NOT DO THIS IF YOU ARE NOT COMFORTABLE WITH WHAT YOU ARE DOING.
	###
	### ONCE YOU START MAKING FORCIBLE CHANGES ON YOUR LOCAL OR HOSTED REPOS, YOU MAY NOT BE ABLE TO UNDO YOUR UNDOs SO GO SLOWLY AND MAKE URE YOU DO THE RIGHT THING
	###

	### ------------------------------------------------------------------

	### Reference: http://stackoverflow.com/questions/1270514/undoing-a-git-push#1270608