skippy

Overview:

• speed 'champ': protobuf
• namespacing: protobuf (beefcake doesn't support it 'out of the box')
• rubyness: beefcake by a nose

notes:

• performance isn't everything, though I was surprised how much protobuf seemed to be ahead. These are very basic benchmarks, and your milage may, and probably will (!), vary. I noticed without strings protobuf was about 1/2 faster, but when including strings, that dropped to about 1/3 faster.
• I like namespacing. If I'm going to go through the 'hassle' of putting a schema and DSL onto my wire definitions, then namespacing is more than a nice-to-have. Beefcake has a way to add it during build-time via the shell ENV, but protobuf wins a bit by just getting 'er done.

skippy

# run from a coreos fleet file; change as you see fit
# NOTE: this shares the /etc folder with docker; ugh!  
# using multiple -v doesn't seem to work (as consul-template 
# does atomic writes, which requires writing a tmp file 
# then moving it).
docker run --rm \
  --name docker-registry \
  -e SERVICE_IGNORE=1 \
  -v /etc:/configs \
  skippy/consul-template \

skippy

#!/bin/bash
# set -eo pipefail

export CONSUL_NUM_INSTANCES=${CONSUL_NUM_INSTANCES:-3}
echo " => stopping consul"
fleetctl stop -block-attempts=10 \
	$(eval echo "consul-server@{1..$CONSUL_NUM_INSTANCES}.service") \
	consul-agent.service

# FIXME: sometimes it takes awhile for systemd to stop things... 

skippy

#cloud-config
---
coreos:
  units:
  - name: update-fleet-metadata.service
    command: start
    content: |-
      [Unit]
      Description=Update Fleet metadata tag
      Before=fleet.service

skippy

#!/usr/bin/env sh

echo "Hello World"

skippy

module MyApp
  class Notifier

    class << self      
      def notify(*args)
        safely_trigger(Airbrake, :notify, args)
      end
      
      def safely_trigger(klass, method, args)
        #simple, safe; heavy but it isn't called very often!

skippy

# NOTES ON CHANGE:
#  * runit_service will launch the service, so put it at the end
#  * because of the immediate restart needs, do some ugly stuff at the end to deal with that
#  * concern: TOO complex; the immediate restarts should not be needed...
#
#
# Cookbook Name:: nginx
# Recipe:: source
#
# Author:: Adam Jacob (<[email protected]>)

skippy

$ knife search node "name:i-2f525a41" -l 
1 items found

Node Name:   i-2f525a41
Environment: development
FQDN:        
IP:          
Run List:    
Roles:       
Recipes      

skippy

window.myApp = window.myApp || {};

(function( myApp, undefined ) {
  var require, define;
  (function () {
    //wrap require.js in our namespace!
    var version = "0.24.0".........
  }());
  
  myApp.require = require;

skippy

      def [](key)
        @current_nesting_level << key

        # We set this to so that we can cope with ||= as a setting.
        # See the comments in []= for more details.
        @has_been_read = true

        # If we have a set type, our destiny is to write
        if @set_type
          a_value = @set_type == :automatic ? value_or_descend(current_automatic, key, auto_vivifiy_on_read) : nil