blalor

Keybase proof

I hereby claim:

• I am blalor on github.
• I am blalor (https://keybase.io/blalor) on keybase.
• I have a public key ASBJhMUPPLE8Bt4qb6oj2khV8Xkz6ylOlVerdzNBi3r0Xgo

To claim this, I am signing this object:

blalor

I hate GMail, but sometimes you gotta. They're notoriously awful at deleting lots of messages at once, as their own search engine will tell you. I had more than 1,000,000 messages I needed to purge and couldn't do it using their own tools. So I wrote my own.

blalor

## chef report handler for Consul
## depends on a chef-client check being registered with the agent
## • pings TTL-style check with ok/warning status on chef run pass/fail
## • stores run report and node attributes in chef/reports/<datacenter>/<consul_node_name>

require "chef/handler"
require "rest_client"

class ConsulHandler < Chef::Handler
    attr_reader :config

blalor

#!/bin/bash

set -e -u

title="$1"

username=$( jq -r .user $HOME/.bitbucket_creds )
password=$( jq -r .passwd $HOME/.bitbucket_creds )

# get repo name from the current repo

blalor

This'll suffice until boot2docker get their shit together and give me VirtualBox shared folder support.

On OS X, just export DOCKER_HOST=tcp://172.28.128.3:4243 and off you go. All exposed ports can be accessed via 172.28.128.3 (assuming that's the IP you get from VirtualBox).

Your entire home directory is mounted under the same path, so from OS X you can do docker run -i -t -v $HOME/devel/some-project:/srv/some-project image /bin/bash and the volume will be mounted as you'd expect. With a caveat: filesystem notifications (inotify and friends) don't get passed along.

blalor

#!/bin/bash
#
# consul        Manage the consul agent
#       
# chkconfig:   2345 95 95
# description: Consul is a tool for service discovery and configuration
# processname: consul
# config: /etc/consul.conf
# pidfile: /var/run/consul.pid

blalor

PoC for a generic HTTP proxy for Docker hosts.

http://myapp.example.com:8080 → http://myapp.dev.docker:8080

blalor

Log into EC2 instances naturally without having to figure out their public hostname ahead of time!

$ ssh ec2-user@web-prod-1.ec2
Last login: Wed Mar 12 22:06:27 2014
[ec2-user@ip-10-158-37-24 ~]$ 

blalor

serving a public yum repo via s3

Steps for creating one or more public Yum repositories served via S3 with write access for the owner only. Don't put the repository in the root of the bucket; you won't be able to serve multiple repositories, and if you choose to enable logging you'll expose those publicly, as well.

The only magic here is the S3 bucket policy.

GPG-signed packages and repo metadata are left as an exercise to the reader.

how to do it

blalor

/* jshint -W064 */
"use strict";

var path   = require("path");
var url    = require("url");
var assert = require("assert");
var semver = require("semver");
var Q      = require("q");

module.exports = function(grunt) {