rkh

# encoding: binary

# Removes any bytes from a string that are not valid UTF-8
class Cleaner
  attr_reader :bytes, :buffer, :outstanding

  def self.clean(str)
    new.tap { |c| c << str }.to_s
  end

purcell

# Monkeypatch fix for https://github.com/rack/rack/issues/386 achieved by
# applying https://github.com/rack/rack/commit/2dfe94071497678c15cfcd8e63663d92f82958e5

raise "remove this fix" if Gem.loaded_specs["rack"].version > Gem::Version.new("1.4.1")

module Rack
  module Utils
    def parse_query(qs, d = nil)
      params = KeySpaceConstrainedParams.new

bhenerey

In a perfect world, where things are done well, not just quickly, I would expect to find the following when joining the company:

Documentation

• Accurate / up-to-date systems architecture diagram

• Accurate / up-to-date network diagram

• Out-of-hours support plan

• Incident management plan

GregSutcliffe

#!/bin/bash
#
# IRC notification post-receive hook.
# Based on https://wiki.icinga.org/display/community/GIT+Commit+Bot
# 
# Author:      Mikael Fridh <frimik@gmail.com>
# Modified by: Greg Sutcliffe <gsutcliffe@ibahn.com
#
# This script pulls out the commit information and sends it to 
# the RemoteCtl plugin in rbot via quassel.office:7268 using

GregSutcliffe

class test {

  # Create the admin repo in the inital call, using defaults
  class { 'gitolite': }

  # Optionally override with your own config and keys
  #class { 'gitolite': }
  #  authfile => 'puppet:///modules/test/admin.conf',
  #  keydir   => 'puppet:///modules/test/admin-keys',
  #}  

jallspaw

Adrian -

I appreciate that you spent time in writing this post. I know I've been up until 2am writing similarly long ones as well. I will take responsibility for having what is likely an irrational response (I blame Twitter for that) to the term "NoOps", but I invite you to investigate why that might be. I'm certainly not the only one who feels this way, apparently, and thus far have decided this issue is easily the largest distraction in my field I've encountered in recent years. I have had the option to simply ignore my opposition to the term, and just let the chips fall where they may with how popular the term "NoOps" may or may not get. I have obviously not taken that option in the past, but I plan to in the future.

You're not an analyst saying "NoOps". Analysts are easy (for me) to ignore, because they're not practitioners. We have expectations of engineering maturity from practitioners in this field of web engineering, especially those we consider leaders. I don't have any expectations from analysts,

rafaelp

# account.rb
class Account < ActiveRecord::Base
  has_many :users
  has_many :services
end

# user.rb
class User < ActiveRecord::Base
  belongs_to :account
end

wycats

Proposal for Improving Mass Assignment

For a while, I have felt that the following is the correct way to improve the mass assignment problem without increasing the burden on new users. Now that the problem with the Rails default has been brought up again, it's a good time to revisit it.

Sign Allowed Fields

When creating a form with form_for, include a signed token including all of the fields that were created at form creation time. Only these fields are allowed.

To allow new known fields to be added via JS, we could add:

ohadlevy

#! /bin/sh
#
USER="admin"
PASS="changeme"
FOREMAN_URL="https://foreman"
FQDN=$1
CHANGED_ATTRIBUTE="host[environment_id]=2"

curl -H "Accept:application/json" -X PUT \
     -k -u $USER:$PASS \

leinaddm

#!/usr/bin/python

# Daniel De Marco - ddm@didiemme.net - 2012-02-23

# suds from https://fedorahosted.org/suds/
import suds
import sys


def get_warr(svctag):