Skip to content

Instantly share code, notes, and snippets.

Avatar

Luke Bakken lukebakken

View GitHub Profile
@lukebakken
lukebakken / Vagrantfile
Last active Nov 19, 2020
Ubuntu 16 + RabbitMQ
View Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
$script = <<SCRIPT
export DEBIAN_FRONTEND=noninteractive
echo "deb https://dl.bintray.com/rabbitmq/debian xenial main" | sudo tee /etc/apt/sources.list.d/bintray.rabbitmq.list
wget -O- https://dl.bintray.com/rabbitmq/Keys/rabbitmq-release-signing-key.asc | sudo apt-key add -
wget https://packages.erlang-solutions.com/erlang-solutions_1.0_all.deb
dpkg -i erlang-solutions_1.0_all.deb
apt-get -yq update
View README.md

Setup

Clone tls-gen, then in the two_shared_intermediates sub-directory:

make CN=HOSTNAME_1
cp result/* path/to/root_ca_1
make clean
make CN=HOSTNAME_2
cp result/* path/to/root_ca_2
View README.md

Run PerfTest with the following arguments:

--rate 1 --producers 1 --consumers 1 --exchange gh-976 --routing-key gh-976
View consumer.go
// This example declares a durable Exchange, an ephemeral (auto-delete) Queue,
// binds the Queue to the Exchange with a binding key, and consumes every
// message published to that Exchange with that routing key.
//
package main
import (
"flag"
"fmt"
"github.com/streadway/amqp"
View repro.py
import logging
from pika import SelectConnection, URLParameters
from threading import Thread
from time import sleep
from argparse import ArgumentParser
class AsyncConnection():
def __init__(self, host):
self.connection_params = URLParameters('amqp://guest:guest@{}:5672/%2F'.format(host))
self.log = logging.getLogger(self.__class__.__name__)
@lukebakken
lukebakken / .gitignore
Created Feb 14, 2018 — forked from sjlongland/test.sh
pika test case: channel close bug
@lukebakken
lukebakken / README.md
Created Feb 9, 2018
Great Burn Proposed Wilderness Comment Period - Feb 12th
View README.md

Great Burn Friends:

It's time to speak out for the Great Burn (deadline Monday, Feb 12). The Nez Perce-Clearwater National Forest is accepting comments for its Forest Plan revision process which will govern how the Great Burn Proposed Wilderness is managed for the next 20 to 30 years.

Will the Great Burn continue to be managed for its fish and wildlife habitat and wilderness values, or will it be opened to motorized and mechanized recreation, mining, or other extractive uses?

Don't delay - the Nez Perce-Clearwater National Forest will only be accepting comments until Monday, February 12th.

Please email your comments to both of these addresses: