Skip to content

Instantly share code, notes, and snippets.

View ryanhiebert's full-sized avatar

Ryan Hiebert ryanhiebert

View GitHub Profile
@ryanhiebert
ryanhiebert / index.test.js
Created December 29, 2017 05:34
Test Probot Pull Request Chaining
// The tests go here
@ryanhiebert
ryanhiebert / index.js
Last active December 29, 2017 05:33
Probot Pull Request Chaining
module.exports = (robot) => {
robot.on('pull_request.closed', async context => {
const {github, payload} = context
const self = payload.pull_request
const owner = payload.repository.owner.login
const repo = payload.repository.name
const base = self.head.ref
const state = 'open'
const per_page = 100
@ryanhiebert
ryanhiebert / socks_sftp.py
Created December 20, 2016 18:54
SFTP via SOCKS Proxy using Paramiko
import paramiko, socks
# PySocks recommends using no arguments,
# because it only supports the defaults anyway.
sock = socks.socksocket()
host, port = '127.0.0.1', 1234
# Set up your proxy information for this socket
sock.set_proxy(

Install cx_Oracle for Python on OS X

Download the following files from Oracle. You'll to login (it's free to register) to download the files.

Create a directory /usr/lib/share/oracle

export ORACLE_HOME=/usr/lib/share/oracle
export VERSION=11.2.0.3.0
export ARCH=x86_64

Keybase proof

I hereby claim:

  • I am ryanhiebert on github.
  • I am ryanhiebert (https://keybase.io/ryanhiebert) on keybase.
  • I have a public key whose fingerprint is 116C 4279 A757 FF3E F73F C631 C4BA 7758 F7B7 4717

To claim this, I am signing this object:

Secure URIs

Right now, HTTP has a problem. This problem isn't unique to HTTP, but it is most aggrevous in HTTP. The problem is Secure URIs.

WARNING: I don't really know the history of the problem. I'm making up a nice story. The points are still valid.

Introduction

In the beggining, there was HTTP. And the whole world saw that it was VERY GOOD. They designated a protocol scheme name for it: http://, so that it would go in a URI like this: http://example.com.