Skip to content

Instantly share code, notes, and snippets.

Sean Johnson pirogoeth

Block or report user

Report or block pirogoeth

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
#!/usr/bin/env python
from sys import argv, stdin, stdout, stderr
from traceback import print_exc
from os import path, isatty
from textwrap import dedent
from collections import Counter
from math import sqrt
import inspect
# Luminance threshold values
lsiden / my-rvm-prompt
Created Jan 8, 2012
Wrapper for rvm-prompt that searches parent directories for files that tell we're in a Ruby project dir or sub-dir
View my-rvm-prompt
# Use this script instead of ~/.rvm/bin/rvm-prompt
# and the output of rvm-prompt will show up in your command prompt
# only if you are in a Ruby project directory.
# see
# and
pirogoeth /
Created Jan 16, 2016 — forked from robinsmidsrod/
Bootstrapping full iPXE native menu with customizable default option with timeout (also includes working Ubuntu 12.04 preseed install)

Add the following chunk to your existing ISC dhcpd.conf file.

if exists user-class and ( option user-class = "iPXE" ) {
    filename "http://boot.smidsrod.lan/boot.ipxe";
else {
    filename "undionly.kpxe";

(or see for a more elaborate setup

simonmcc / route53DynDNS.bash
Created Jul 22, 2012 — forked from natlownes/route53DynDNS.bash
Amazon Route 53 Dynamic DNS Updater Script
View route53DynDNS.bash
# This script requires xpath to parse part of the output
# on CentOS/RedHat/Amazon Linux:
# sudo yum install perl-XML-XPath
# also, (from
# expects your secrets to be in ~/.aws-secrets
# using a file format like this (from
massenz / README.rst
Last active Aug 8, 2017
Apache Mesos build and install scripts; optionally runs the Master/Slave locally and executes a demo (C++) framework against it, to validate it all went according to plan
View README.rst

Apache Mesos Build scripts

The `Getting started`_ instructions are a good start (no surprise there!) but are somewhat incomplete and currently look a bit outdated (I plan to fix them soon): however, the outcome has been that I have struggled more than I felt necessary in building and running Mesos on a dev VM (Ubuntu 14.04 running under VirtualBox).

Some of the issue seem to arise from the unfortunate combination of Mesos Master trying to guess its own IP address, the VM being (obviously) non-DNS resolvable and, eventually, the Slave and the Framework failing to properly communicate with the Master.

In the process of solving this, I ended up automating all the dependencies installation, building and running the framework; I have then broken it down into the following modules to make it easier to run only parts of the process.

technicalpickles / inspector
Last active Aug 10, 2017
hubot with debugging
View inspector
set -e
for opt in $* ; do
case "$opt" in
--debug) hubot_debug="coffee --nodejs --debug";;
arvids / PKGBUILD
Last active Dec 3, 2017
polybar PKGBUILD
The polybar package has been updated so this is no longer needed.
bzed / pfsense.grok
Created Mar 10, 2015
Logstash pfsense pattern
View pfsense.grok
# GROK Custom Patterns (add to patterns directory and reference in GROK filter for pfSense events):
# GROK Patterns for pfSense 2.2 Logging Format
# Created 27 Jan 2015 by J. Pisano (Handles TCP, UDP, and ICMP log entries)
# Edited 14 Feb 2015 by E. Paul
# Edited 10 Mar 2015 by Bernd Zeimetz <>
# taken from
clarkdave / logstash-sentry.rb
Last active Oct 25, 2018
(Logstash) Sentry output plugin
View logstash-sentry.rb
# The MIT License (MIT)
# Copyright (c) 2014 Dave Clark
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
asiegman / nginx.conf
Created Jan 29, 2015
nginx logstash output
View nginx.conf
# Output json-esque output for logstash to parse easily.
http {
# ...
log_format logstash_json '{"@timestamp": "$time_iso8601", '
'"remote_addr": "$remote_addr", '
'"remote_user": "$remote_user", '
'"body_bytes_sent": "$body_bytes_sent", '
'"request_time": "$request_time", '
You can’t perform that action at this time.