How to implement a custom search for Hugo usig Gruntjs and Lunrjs.
Install the following tools:
import Foundation | |
go(println("in a thread")) | |
// buffered channel | |
var c = Chan(buffer:20) | |
// sending routing | |
go { | |
while(true) { |
// | |
// Goroutines.swift | |
// TestGoer | |
// | |
// Created by Doug Marcey on 6/11/14. | |
// Copyright (c) 2014 Doug Marcey. All rights reserved. | |
// | |
import Foundation |
package main | |
import ( | |
"fmt" | |
"io/ioutil" | |
"os" | |
"path/filepath" | |
"strings" | |
) |
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
OK, you can pretty much ignore what I wrote below this update, because it doesn't really apply anymore.
I wrote this over a year ago, and at the time I had spent a couple of weeks trying to get Kafka 0.8 working with .NET and then Node.js with much frustration and very little success. I was rather angry. It keeps getting linked, though, and just popped up on Hacker News, so here's sort of an update, although I haven't used Kafka at all this year so I don't really have any new information.
In the end, we managed to get things working with a Node.js client, although we continued to have problems, both with our code and with managing a Kafka/Zookeeper cluster generally. What made it worse was that I did not then, and do not now, believe that Kafka was the correct solution for that particular problem at that particular company. What they were trying to achieve could have been done more simply with any number of other messaging systems, with a subscriber reading messages off and writing
#!/bin/bash | |
# Don't put duplicate lines in the history | |
export HISTCONTROL=ignoredups | |
# Store a lot history entries in a file for grep-age | |
shopt -s histappend | |
export HISTFILE=~/long_history | |
export HISTFILESIZE=50000 |
So one of the painful points of using docker
on OS X is that you need to run a virtualbox VM, which often suffers from performance issues. With xhyve, a OS X virtualization system, and docker-machine-xhyve you can now have docker
use the native OS X hypervisor to run containers.
No more dealing with virtualbox shenanigans!
In this script, I've also set up a way to autoconfigure terminal sessions to load docker's environment vars (dependent on docker-machine
) so you do not have to run eval $(docker-machine env whatever)
every time you open a new terminal window.
package main | |
import ( | |
"encoding/json" | |
"flag" | |
"fmt" | |
"io" | |
"log" | |
"net/http" |