Chase Southard chaserx

Configuring Proxmox VE node as client for remote NUT server

Network UPS Tools User Manual

apt-get install nut

Edit /etc/nut/nut.conf:

RailsConf 2015 Schedule

RailsConf 2015 Room 202 Day 1

The Ten Commandments of Egoless Programming

Understand and accept that you will make mistakes. The point is to find them early, before they make it into production. Fortunately, except for the few of us developing rocket guidance software at JPL, mistakes are rarely fatal in our industry. We can, and should, learn, laugh, and move on.
You are not your code. Remember that the entire point of a review is to find problems, and problems will be found. Don’t take it personally when one is uncovered.
No matter how much "karate" you know, someone else will always know more. Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it’s not needed.
Don’t rewrite code without consultation. There's a fine line between "fixing code" and "rewriting code." Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer.

#How I built an audio book reader for my nearly blind grandfather

Tweet this - Follow me

Last year, when visiting my family back home in Holland, I also stopped by my grand-parents. My grand-father, now 93 years old, had always been a very active man. However, during the presceding couple of months, he'd gone almost completely blind and now spent his days sitting in a chair. Trying to think of something for him to do, I suggested he try out audio books. After finally convincing him -- he said audio books were for sad old people -- that listening to a well performed recording is actually a wonderful experience, I realized the problem of this idea.

####The problem with audio devices and the newly blind. After my first impulse to jump up and go buy him an

How to use Tim Pope’s Pathogen

I’ll assume you are on Linux or Mac OSX. For Windows, replace ~/.vim/ with $HOME\vimfiles\ and forward slashes with backward slashes.

The idea

Vim plugins can be single scripts or collections of specialized scripts that you are supposed to put in “standard” locations under your ~/.vim/ directory. Syntax scripts go into ~/.vim/syntax/, plugin scripts go into ~/.vim/plugin, documentation goes into ~/.vim/doc/ and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.

This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under ~/.vim/bundle/, where each directory simulates the standard structure of your ~/.vim/ directory.

	AllCops:
	RunRailsCops: true

	# Commonly used screens these days easily fit more than 80 characters.
	Metrics/LineLength:
	Max: 120

	# Too short methods lead to extraction of single-use methods, which can make
	# the code easier to read (by naming things), but can also clutter the class
	Metrics/MethodLength:

	# Be sure to save your config files. Optional but I do:
	sudo cp /etc/postgresql/9.3/main/postgresql.conf ~
	sudo cp /etc/postgresql/9.3/main/pg_hba.conf ~

	# Package repo (for apt-get)
	wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc \| sudo apt-key add -
	sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main" >> /etc/apt/sources.list.d/postgresql.list'

	# Also probably optional but I like to update sources and upgrade
	sudo apt-get update

	# The blog post that started it all: https://neocities.org/blog/the-fcc-is-now-rate-limited
	#
	# Current known FCC address ranges:
	# https://news.ycombinator.com/item?id=7716915
	#
	# Confirm/locate FCC IP ranges with this: http://whois.arin.net/rest/net/NET-165-135-0-0-1/pft
	#
	# In your nginx.conf:

	location / {

	brews = []
	out = IO.popen("brew list", "r") do \|io\|
	brews = io.read.split "\n"
	end

	def parse(brew, brew_info)
	in_options = false
	print "brew reinstall -v #{brew} "
	brew_info.split("\n").each do \|m\|
	#puts m.inspect