Session IPA

This is one of my go-to recipes. Light, easy to drink, still hoppy, and tasty. It's been through many iterations, I think I'm coming close to the hop flavor and aroma that will be it's final form.

Session IPA (11.5 gal.)

  • 13# 2-Row
  • 2.5# 40l
  • 1# Cara-pils
Mash at 148º for 30 minutes
  • 2 oz. Magnum FWH (30 minute boil)
  • 2 oz. Cascade, 5 min.
  • 2 oz Palisade, flame-out, 10 minute steep
2 cans Imperial A01 House

Brew Day - NW Red

Got to brew a pretty standard red on Sunday, but gave it just enough of a twist to make it 'NW' style. Starting recipe was the Irish Red out of Brewing Classic Styles (upped to 12 gallons).

NW Red Recipe

  • 20# Great Western NW Pale Malt
  • 12oz Great Western Crystal 40l
  • 12oz Great Western Crystal 120l
  • 12oz Light Roasted Barley (300l)
Mash at 154º F for ~45 minutes
  • 1.5oz Magnum pellet at 30 minutes

WAHA Cider Pressing

On October 10th, members of WAHA clubs gathered near Castle Rock, WA for our annual cider-pressing. This year was a record on many fronts. We had 13 totes of apples (that’s 11,000 pounds) to process, over 90 individuals signed up to receive cider, and we worked through a storm like no other.

The end result was ~560 gallons of cider from Gala apples, and a whole bunch of tired homebrewers.

tracking authenticated Drupal traffic in Varnish

As part of the performance and load testing suite I am building for a client, they asked that it accurately reflect the percentage of traffic which is logged in. Sure, no problem, we told them. But how do we get this? Really, their setup provided no easy way to collect this info (multi-site with ~200 sites). The Google Analytics module *could* be used, as it provides custom variables and we could then use a token with the users role. But, that would require building out a feature, deploying it, and enabling.

Caching pages in Varnish with HTTP Basic Authentication

Normally, if Varnish sees that a page has HTTP Basic Auth on it, it will immediately trigger a pass to the backend. This was causing some performance issues with the staging setup for one of our clients. They had a (smaller) mirrored setup of their production systems, just for staging. Varnish -> 2 Apache backends -> 1 DB server. But, all their staging sites have HTTP Basic Authentication on them, to keep the public's prying eyes away. Our sys-admin discovered this article, and we are working on implementing this as a solution for them right now.

tmux. do it. do it now!

I've been relying on GNU Screen for many many years. Figured it was 'good enough' and met my basic needs. But, as I spend more and more time on the command line, I find myself getting tired of SSHing in to the same server multiple times, to open connections to other servers in our network. For example, when one of our clients wants to launch one of their sites, I have to SSH in to 5 different servers to stop Puppet, test the update, have Puppet apply the changes, test things, and restart Puppet.