tgautier

#!/usr/bin/env bash

KUBEAPI=127.0.0.1:8001/api/v1/nodes

function getNodes() {
  curl -s $KUBEAPI | jq -r '.items[].metadata.name'
}

function getPVCs() {
  jq -s '[flatten | .[].pods[].volume[]? | select(has("pvcRef")) | '\

tgautier

types:
  addition: "93c95c"
  environment: "fad9c9"
  experience: "ffc27a"
  feedback: "cc317c"
  improvement: "63c0fd"
  inactive: "d3dbe2"
  mindless: "fef2c0"
  pending: "fbc92f"
  platform: "c1d5f1"

tgautier

# With thanks to https://github.com/optoro/activerecord-callback_notification for original inspiration
if Rails.env.development?
  module ActiveRecord
    module CallbackNotifications
      extend ActiveSupport::Concern

      module ClassMethods

        def notify_all_callbacks
          # Make sure all models are loaded before trying to enumerate

tgautier

### INSTALLATION NOTES ###
# 1. Install Homebrew (https://github.com/mxcl/homebrew)
# 2. brew install zsh
# 3. Install OhMyZsh (https://github.com/robbyrussell/oh-my-zsh)
# 4. brew install reattach-to-user-namespace --wrap-pbcopy-pbpaste && brew link reattach-to-user-namespace
# 5. Install iTerm2
# 6. In iTerm2 preferences for your profile set:
#      Character Encoding: Unicode (UTF-8)
#      Report Terminal Type: xterm-256color
# 7. Put itunesartist and itunestrack into PATH

tgautier

# -*- encoding: utf-8 -*-

Gem::Specification.new do |s|
  s.name        = 'parallel_assets_compiler'
  s.version     = '0.2.0'
  s.platform    = Gem::Platform::RUBY
  s.author      = 'Jørgen Orehøj Erichsen'
  s.email       = 'joe@erichsen.net'
  s.summary     = 'Compile assets in parallel'
  s.description = 'Compile assets in parallel to speed up deployment'

tgautier

Devise / Warden Tagged logging

I wrote a middleware (actually two, but they do the same with different implementations) that logs information about signed in scopes in a Rails + Devise application. The solution works with multiple logins (like having a person logged both as an Admin and a User). I tested against Rails 4 and Devise HEAD, but it should work fine in any Rails 3 application.

This solution doesn't use the log_tags configuration option since it isn't very helpful when you need to retrieve information stored in cookies/session. That information isn't 'ready' when the Rails::Rack::Logger is executed, since it happens way down in the middleware chain.

Add one of the following implementations to your application load path and use the following configuration to add the middleware to your application stack:

# application.rb

tgautier

If you're writing web applications with Ruby there comes a time when you might need something a lot simpler, or even faster, than Ruby on Rails or the Sinatra micro-framework. Enter Rack.

Rack describes itself as follows:

Rack provides a minimal interface between webservers supporting Ruby and Ruby frameworks.

Before Rack came along Ruby web frameworks all implemented their own interfaces, which made it incredibly difficult to write web servers for them, or to share code between two different frameworks. Now almost all Ruby web frameworks implement Rack, including Rails and Sinatra, meaning that these applications can now behave in a similar fashion to one another.

At it's core Rack provides a great set of tools to allow you to build the most simple web application or interface you can. Rack applications can be written in a single line of code. But we're getting ahead of ourselves a bit.

tgautier

git config --global alias.ksreview '!f() { local SHA=${1:-HEAD}; local BRANCH=${2:-master}; if [ $SHA == $BRANCH ]; then SHA=HEAD; fi; git difftool -y -t Kaleidoscope $BRANCH...$SHA; }; f'

tgautier

require 'singleton'

# outputs a colored call-trace graph to the Rails logger of the lines of ruby code
# invoked during a single request.
#
# Example:
#
# 1) Make sure this file is loaded in an initializer
#
# 2) Add the following to your application.rb in Rails3:

tgautier

from django.db.models.signals import post_init

def track_data(*fields):
    """
    Tracks property changes on a model instance.
    
    The changed list of properties is refreshed on model initialization
    and save.
    
    >>> @track_data('name')